Skip to main content
Glama

Search Tools

search_tools
Read-onlyIdempotent

Discover the tools reachable with your current authorization, as TypeScript function declarations (external_) for use inside execute_typescript. Call with no arguments to list everything reachable, or a query to narrow it: a word of a tool name or description ("subscriber"), or a plain question in the user's words ("send a push notification to my users"), which returns the few tools that answer it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
queryNoA word of a tool name or description (case-insensitive substring), or a plain question in the user's words

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Free-text filter over tool name/description (case-insensitive substring)"New value: +"A word of a tool name or description (case-insensitive substring), or a plain question in the user's words"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real context beyond them: results are authorization-scoped and shaped as typed function declarations for execute_typescript, which tells the agent what it is getting back.

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

Conciseness5/5

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

Two sentences, front-loaded with the core purpose before branching into the two call modes. The example words and question are compact illustrations that earn their 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?

With no output schema, the description carries the return-value burden and does so by naming the TypeScript declaration form and the external_<name> convention. It doesn't mention result limits or how large 'list everything' can be, which would matter for a discovery tool, but nothing critical for calling it is missing.

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

Parameters3/5

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

Schema description coverage is 100% and the single parameter's schema text is essentially identical to the description's wording, so the description adds little new meaning about the parameter itself. The one addition, that a plain question 'returns the few tools that answer it', describes results rather than parameter syntax.

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 ('Discover the tools reachable with your current authorization') and names the concrete output form (TypeScript function declarations, external_<name>). It also distinguishes itself from its only sibling by saying the declarations are meant for use inside execute_typescript.

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

Usage Guidelines4/5

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

Gives two explicit modes: call with no arguments to list everything reachable, or with a query to narrow. It doesn't spell out exclusions or when to prefer browsing over querying (e.g. which mode to pick for large result sets), but the usage context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources