Skip to main content
Glama

search_tools

Discover available capabilities by querying tool names and domains, then activate matching tools so you can call them without assuming a capability is unavailable.

Instructions

Search 736 tools across 36 capability domains. This includes built-in tools plus any loaded plugin/workflow tools (0 currently loaded). In search-tier sessions, call this before assuming a capability is unavailable. Use activate_tools for exact matches, activate_domain for an entire domain. Domains: browser (85) | memory (75) | native-emulator (57) | binary-instrument (46) | network (38) | process (29) | tls-inspector (29) | adb-bridge (26) | core (25) | debugger (21) | exploit-dev (21) | v8-inspector (21) | protocol-analysis (20) | platform (18) | maintenance (17) | streaming (17) | wasm (17) | dart-inspector (16) | syscall-hook (15) | instrumentation (13) | workflow (13) | coordination (12) | canvas (11) | proxy (11) | trace (10) | webgpu (10) | cross-domain (8) | mojo-ipc (8) | transform (8) | extension-registry (7) | graphql (7) | sourcemap (7) | native-bridge (6) | encoding (5) | tasks (4) | session (3). Query tip: before searching, distill your intent into key concepts (action verb + target + domain). The engine combines token matching, fuzzy names, profile context, and optional static embeddings.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesBefore calling, distill your intent into 2-5 key concepts: what action, on what target, in which domain. Pass only those distilled keywords — not the original user request.
top_kNoMax results to return (default: 10, max: 30)
auto_activateNoAuto-activate found tools so they are immediately callable. Set false to only search without activating (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / auto_activate
      Added value: +{
      +  "description": "Auto-activate found tools so they are immediately callable. Set false to only search without activating (default: true)",
      +  "type": "boolean"
      +}
  2. First observedv0.3.0

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full load and mostly succeeds: it discloses the search-tier session rule, the matching engine's behavior (token matching, fuzzy names, profile context, optional static embeddings), and that results can be auto-activated to become callable. It stops short of describing the result shape (names, scores, descriptions) or whether activation persists until explicitly deactivated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then routing alternatives, then the domain inventory, then the query tip — a sensible priority order. The 36-domain list consumes most of the length but is genuinely useful for picking a domain to activate, so it mostly earns its space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a search tool with no output schema, the description covers corpus size, domain breakdown, routing alternatives, and query construction — enough to call it correctly. The notable remaining gap is what a result entry looks like and how ranking is surfaced.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3, but the description adds genuine value on the query parameter by telling the agent to distill intent into 2-5 concepts (action + target + domain) rather than passing the raw request. It does not restate top_k or auto_activate, which the schema already covers well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search 736 tools across 36 capability domains') plus the corpus composition: built-in tools plus loaded plugin/workflow tools. It explicitly distinguishes itself from activate_tools (exact match) and activate_domain (whole domain), so an agent can pick it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-call guidance ('in search-tier sessions, call this before assuming a capability is unavailable') and names the two alternatives with the conditions that select them. The 'Query tip' adds a concrete how-to-use instruction for constructing the argument.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.