You set the scope
Access your team controls
Choose the connected accounts and enabled actions your agent can use. Search works within that configured access.
Explore Permission Policies
The Best
Tool Discovery
for AI Agents
Two tools instead of hundreds. Your agent searches by meaning, loads only the actions it needs, and keeps its context for reasoning.
#1 Tool search on ToolRet-full44,453 tools · 7,961 queries
93.8% Search accuracyMetaTool · nDCG@5
3.8× Cheaper per requestTool Search vs every tool loaded · 824 tasks
Give Maya the approved Finance access and update her IT request.
Two tools do the work
tool_search found 5 of 247 actions tool_execute ran all 5 on StackOne Done. Maya's group membership is updated in Okta. Her existing ServiceNow request records the change.
5 actions executed · 97% fewer tokens on tool definitions
Companies already connected through StackOne
Semantic tool search benchmarks. Custom-trained for
better tool selection.
Our fine-tuned retrieval model leads three public tool-retrieval benchmarks against Anthropic Tool Use, AgentCore Gateway and keyword search.
MetaTool
A public benchmark: 200 single-tool APIs and 2,000 queries, the smallest of the three, testing basic retrieval quality.
Benchmark on GitHub ↗ (opens in new tab)ToolBench
A public benchmark from OpenBMB: 10,439 real-world API tools and 451 queries across three instruction types.
Benchmark on GitHub ↗ (opens in new tab)ToolRet-full
A public tool-retrieval benchmark: 44,453 tools across code, web and custom sets, and 7,961 queries with graded relevance.
Benchmark on GitHub ↗ (opens in new tab) ·
| Benchmark | Metric | Method | Score | Source |
|---|---|---|---|---|
| MetaTool | nDCG@5 | StackOne | 93.8% | Measured, 2,000 queries |
| MetaTool | nDCG@5 | Anthropic Tool Use | 91.3% | Measured, 30-query sample |
| MetaTool | nDCG@5 | AgentCore Gateway | 72.8% | Measured, 2,000 queries |
| MetaTool | nDCG@5 | BM25 | 38.5% | Measured, 2,000 queries |
| ToolBench | Hit@5 | StackOne | 74.3% | Measured, 451 queries |
| ToolBench | Hit@5 | Anthropic Tool Use | 40.0% | Measured, 10-query sample |
| ToolBench | Hit@5 | AgentCore Gateway | 34.1% | Measured, 451 queries |
| ToolBench | Hit@5 | BM25 | 26.6% | Measured, 451 queries |
| ToolRet-full | nDCG@10 | StackOne | 54.4% | Measured, 7,961 queries |
| ToolRet-full | nDCG@10 | Qwen3-8B | 46.2% | Published by the benchmark authors |
| ToolRet-full | nDCG@10 | BM25s | 36.4% | Published by the benchmark authors |
| ToolRet-full | nDCG@10 | AgentCore Gateway | 22.8% | Measured, 7,961 queries |
MetaTool 93.8% nDCG@5 against Anthropic Tool Use 91.3%; ToolBench 74.3% Hit@5 against Anthropic Tool Use 40.0%; ToolRet-full 54.4% nDCG@10 against Qwen3-8B 46.2%
How MCP tool search works. From 1,000 agent tools
to 2
tool_search finds the right actions. tool_execute runs them. Your agent loads what the task needs, leaving more context for reasoning.
Your agentconnected to
Workday
Okta
ServiceNowYour agent's context
Without Tool Search
≈74ktokens in context
With Tool Search
≈900tokens in context
82×Send a prompt to watch the context fill.
What can I help with?
Pick an example below and send it.
Interactive simulation. Pick a prompt, then send it.
Zendesk ticket 1842 to Engineering and notify the incident channel.Check MMaya's finance onboarding and route any mismatch to HR.Verify SSam's hiring and HR records, then send People Ops the onboarding handoff.Check BILL-1042 against PO-2087 and route any mismatch to AP.Check AAcme's overdue invoice and create a follow-up for its account owner. You:
Give MMaya the approved Finance access and update her IT request.
I'll find the right actions, then work through the request.
Request context
An approved ServiceNow request identifies Workday employee 21001 and the Finance - NetSuite access group.
- Verify the employeeWorkday
tool_searchFinding the action…Found
workday_list_workerstool_executeMaya is an active employee; work email verified. - Match her identityOkta
tool_searchFinding the action…Found
okta_list_userstool_executeFound the Okta account matching her work email. - Find the approved groupOkta
tool_searchFinding the action…Found
okta_list_groupstool_executeFound the approved Finance group, managed in Okta. - Apply the approved accessOkta
tool_searchFinding the action…Found
okta_add_user_to_grouptool_executeAdded Maya to the approved group. - Record the changeServiceNow
tool_searchFinding the action…Found
servicenow_update_tasktool_executeRecorded the change in the existing IT request.
Done.
Maya's group membership is updated in Okta. Her existing ServiceNow request records the change.
Only 5 action schemas loaded, as they were needed.
You:
Escalate Zendesk ticket 1842 to Engineering and notify the incident channel.
I'll find the right actions, then work through the request.
Request context
The request supplies the Zendesk ticket ID, Jira project key and issue type, and Slack incident channel ID. The agent carries the ticket reference into the engineering issue and notification.
- Read the customer issueZendesk
tool_searchFinding the action…Found
zendesk_get_ticketstool_executeRetrieved the ticket description, priority and customer impact. - Create the engineering issue
Jiratool_searchFinding the action…Found
jira_create_issuetool_executeCreated a Jira issue with the customer impact and Zendesk reference. - Notify the incident channel
Slacktool_searchFinding the action…Found
slack_send_messagetool_executePosted the escalation with links to both records.
Done.
Engineering has a Jira issue linked to the Zendesk ticket, and the incident channel has the escalation details.
Only 3 action schemas loaded, as they were needed.
You:
Check MMaya's finance onboarding and route any mismatch to HR.
I'll find the right actions, then work through the request.
Request context
The onboarding request supplies Workday employee 21001 and NetSuite employee 846. The agent verifies they refer to the same person before comparing records.
- Read the HR recordWorkday
tool_searchFinding the action…Found
workday_list_workerstool_executeMaya's HR record lists Finance as her department. - Check the finance profile
NetSuitetool_searchFinding the action…Found
netsuite_get_employeetool_executeSame employee, but the department differs from Workday. - Resolve the HR teamServiceNow
tool_searchFinding the action…Found
servicenow_list_groupstool_executeFound the HR Operations assignment group. - Route the discrepancyServiceNow
tool_searchFinding the action…Found
servicenow_create_tasktool_executeReview task assigned to HR Operations
Done.
A department mismatch is recorded in a ServiceNow task assigned to HR Operations, with evidence from both employee records.
Only 4 action schemas loaded, as they were needed.
You:
Verify SSam's hiring and HR records, then send People Ops the onboarding handoff.
I'll find the right actions, then work through the request.
Request context
The approved handoff supplies a Greenhouse candidate ID, BambooHR employee ID and People Ops Slack channel ID. The agent verifies the records refer to the same hire before summarizing them.
- Find the approved candidate
Greenhousetool_searchFinding the action…Found
greenhouse_list_candidatestool_executeFound Sam using the candidate ID from the handoff. - Confirm the hiring statusGreenhouse
tool_searchFinding the action…Found
greenhouse_list_applicationstool_executeThe matching application is marked hired. - Check the HR record
BambooHRtool_searchFinding the action…Found
bamboohr_get_employeetool_executeMatched the approved hire to the employee record and start date. - Send the handoffSlack
tool_searchFinding the action…Found
slack_send_messagetool_executePosted the verified hiring and HR details to People Ops.
Done.
People Ops receives the confirmed hiring status and HR record needed to start Sam's onboarding.
Only 4 action schemas loaded, as they were needed.
You:
Check BILL-1042 against PO-2087 and route any mismatch to AP.
I'll find the right actions, then work through the request.
Request context
The agent resolves document numbers to NetSuite internal IDs, compares the bill and purchase order, then routes the exception to Accounts Payable.
- Resolve the documentsNetSuite
tool_searchFinding the action…Found
netsuite_execute_suiteql_querytool_executeFound the matching bill and purchase order in NetSuite. - Read the vendor billNetSuite
tool_searchFinding the action…Found
netsuite_get_vendor_billtool_executeRetrieved the vendor bill and its line items. - Compare the purchase orderNetSuite
tool_searchFinding the action…Found
netsuite_get_purchase_ordertool_executeSame vendor, but a line-item amount does not match. - Find Accounts PayableServiceNow
tool_searchFinding the action…Found
servicenow_list_groupstool_executeFound the Accounts Payable assignment group. - Route the exceptionServiceNow
tool_searchFinding the action…Found
servicenow_create_tasktool_executeException task assigned to Accounts Payable
Done.
A bill-line mismatch is recorded in a ServiceNow task for Accounts Payable, with references to the bill and purchase order.
Only 5 action schemas loaded, as they were needed.
You:
Check AAcme's overdue invoice and create a follow-up for its account owner.
I'll find the right actions, then work through the request.
Request context
The collection request supplies a Xero invoice ID, the matching Salesforce account ID and the Finance Slack channel ID. The agent checks the customer identity and due date before creating the follow-up.
- Check the invoice
Xerotool_searchFinding the action…Found
xero_get_invoicetool_executeThe invoice is overdue and still has an outstanding balance. - Find the account owner
Salesforcetool_searchFinding the action…Found
salesforce_get_accounttool_executeVerified the matching customer and read the account owner ID. - Create the follow-upSalesforce
tool_searchFinding the action…Found
salesforce_create_tasktool_executeAssigned a collection task to the account owner with the invoice reference. - Update FinanceSlack
tool_searchFinding the action…Found
slack_send_messagetool_executePosted the balance and collection-task reference to Finance.
Done.
The Salesforce account owner has a collection task, and Finance has the invoice balance and follow-up reference.
Only 4 action schemas loaded, as they were needed.
Dynamic tool discovery with Weave. The right tools.
And the path between them.
Advanced Tool Search pairs fine-tuned embeddings with Weave, our action graph built from connector data and past executions. It maps which action supplies each input across apps, so the agent gets the path and not just the target, and finishes in fewer turns.
It runs the paths behind employee onboarding, ticket triage and deal risk scoring.
Input dependencyFrequently pairedTarget action
Deferred tool loading in any agent. Connect once and
leave Tool Search on.
Add StackOne to your MCP client. Tool Search is enabled by default.
MCP server URL
Paste this URL into your MCP client.
- Add the MCP server URL.
- Sign in and choose your accounts.
- Leave Load tools when needed on.
Using a token-based MCP URL?
Add tool-mode=search_execute to your existing api.stackone.com/mcp URL. Developer guide (opens in new tab).
Enabled by default
Select accounts
Choose the accounts and actions Claude can access.
Accounts Select All (3)
Search Accounts...
Link Account
Beam Notion • 35 Actions • Updated Jul 28, 2026 
Beam Salesforce • 380 Actions • Updated Jul 28, 2026 
Beam SAP S/4HANA • 117 Actions • Updated Jul 28, 2026 Load tools when needed
Your agent looks up the right action when it needs one, instead of loading
all 532 up front. Keeps it fast and inside its context limit.
Back
Authorize
3 accounts selected 532 actions selected
On by defaultTurned off
Load tools when needed Your agent looks up the right action when it needs one, instead of loading every action up front. Keeps it fast and inside its context limit. Every action loads into the agent up front. More of the context window goes on definitions, but the agent sees every tool at once.
Guardrails for enterprise tool access. Your agent acts and
you keep control.
From discovery to execution, the connection to your systems stays managed by StackOne.
StackOne handles the calls
Execution handled by StackOne
Your agent chooses the action and parameters. StackOne handles provider authentication and runs the API calls on the server.
Explore the execution engineScreen the response
Protect the model's context
Configure Defender to screen returned tool content for prompt injection before it reaches the model.
Explore response protection
Works in your MCP client
or your own agent.
Choose your MCP client
Add one server URL and Tool Search is on. Nothing to install, no tool list to maintain.
Build with the StackOne SDK
The same two tools, tool_search and tool_execute, in your own agent loop with any framework.
import { StackOneToolSet } from "@stackone/ai";
const toolset = new StackOneToolSet({ search: {} });
// Two tools reach the model: tool_search and tool_execute
const tools = await toolset.openai({
mode: "search_and_execute",
accountIds: ["acc_123"],
}); Install
npm install @stackone/ai from stackone_ai import StackOneToolSet
toolset = StackOneToolSet(search={"method": "auto"})
# Two tools reach the model: tool_search and tool_execute
tools = toolset.openai(
mode="search_and_execute",
account_ids=["acc_123"],
) Install
pip install stackone-ai AI Tool Search Resources
Blog
Building Semantic Search for 32,000+ Actions
How enriched embeddings reach 84% Hit@5 across 9,340 actions, and why reranking did not help.
Blog
MCP Tool Search: BM25, TF-IDF, and Hybrid
The evaluation behind our local fallback search: 2,700 test cases across 270 tools.
Blog
How to Reduce MCP Token Usage by 96 to 99%
Four strategies, from schema compression to code execution, and the 460x reduction from search-first discovery.
Blog
Why AI Agents Kill Their Own Context Windows
How tool schemas, API responses, and multi-step workflows compound to exhaust your agent's reasoning space.
Frequently Asked Questions
What is a context window in AI, and why does it matter for tool use?
A context window is the token budget an LLM has for a request, including instructions, tool definitions, messages and results. Loading an entire tool catalog uses that budget before the agent starts reasoning. StackOne Tool Discovery loads action schemas as needed. See Advanced Tool Search in the docs.
How does semantic tool search work?
Semantic tool search uses a fine-tuned bi-encoder model to match natural language queries against tool descriptions by meaning, not keywords. For example, the query "give an employee access to the Finance group" can match
okta_add_user_to_group. In our connector-scoped evaluation, with the connector known, the top result was the correct tool 92.8% of the time. This measures tool retrieval, not successful completion of the full task.How is semantic search different from keyword search like BM25?
Keyword search like BM25 matches terms in the query and tool description. StackOne trains its semantic model to match the requested task even when the wording differs from the action name. The SDK's
auto mode uses semantic first and falls back to BM25+TF-IDF locally if the API is unreachable.What is StackOne Weave?
Weave is the dependency graph behind StackOne tool search. It maps input sources ahead of time so a result can include the actions needed to call it. For example,
okta_add_user_to_group needs an Okta userId and groupId; okta_list_users and okta_list_groups supply them. The agent still plans and executes the task, including matching identities across connectors.How do I enable tool search on my StackOne MCP server?
Advanced Tool Search is on by default. Paste
https://mcp.stackone.com/mcp into your client, sign in, and keep the Load tools when needed toggle on when you authorize. Your agent then sees two tools, tool_search and tool_execute, instead of hundreds of individual definitions. On token-based URLs, add tool-mode=search_execute to api.stackone.com/mcp instead. Neither route needs a migration or code changes. See StackOne MCP.Does StackOne MCP tool search work with Claude, ChatGPT, and Cursor?
Yes. Paste
https://mcp.stackone.com/mcp into any MCP client, including Claude, ChatGPT, Cursor, Windsurf, VS Code and Zed, then sign in with OAuth and authorize. Tool search is on by default, so the agent sees tool_search and tool_execute instead of hundreds of definitions. No SDK or code changes needed on the client side. See StackOne MCP for client guides.When should I NOT use tool search?
If your agent uses fewer than 10 tools, static definitions work fine: context cost is negligible and tool availability is deterministic. Tool search adds value when connecting multiple systems where tool count exceeds what fits in the context window, or when you need semantic search across connectors.
What are the current limitations?
StackOne semantic tool search requires network connectivity. The SDK can fall back to local keyword search, which may return different results. Search retrieves possible actions; the agent still supplies parameters, verifies records and handles action results. Code Mode is a separate execution capability.
Let your agent find the tools it needs.
Connect your enterprise apps and put Tool Search to work.