Skip to main content
Glama

discover_tools

Find and enable relevant tools and return their schemas. When the client cannot refresh its catalog, run supported read/index calls; source edits are excluded.

Instructions

Discover or enable experts and return their schemas. If the client cannot refresh its catalog, call runs a supported read/index tool; never source edits.

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": "discover_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
callNoIf the client cannot refresh tools, execute a supported read/index tool using its discovered schema. Pass root outside call; source edits are excluded.
rootNoAbsolute project root. Omit only where this session started; required elsewhere and on every subagent call.
limitNoMaximum discovery matches; default 5.
queryNoPurpose, e.g. rename, tests, or memory.
enableNoExact tool names to add to this session's catalog.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.0
    • changedInput schema / properties / root / description
      Previous value: -"Absolute project root. Required with linked worktrees; subagents must pass their own worktree root on every call."New value: +"Absolute project root. Omit only where this session started; required elsewhere and on every subagent call."
  2. First observedv1.4.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, and the description adds a genuinely useful constraint beyond them: the fallback execution path only runs read/index tools and excludes source edits, which explains why the tool is non-read-only yet non-destructive. It does not state that enabling mutates the session catalog or whether that change persists, leaving the main mutation under-explained.

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

Conciseness3/5

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

The purpose is front-loaded in the first sentence, but the second sentence is telegraphic and awkwardly compressed ('call runs a supported read/index tool; never source edits'), which forces the reader to reparse it. No sentence is purely filler, but the phrasing costs clarity.

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

Completeness3/5

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

With five parameters including a nested free-form `call` object and no output schema, the description covers the discovery contract but not the interaction between query, limit, and enable, nor what the returned schemas look like or how they should be applied. Annotations exist, so the safety gap is partially covered, but the execution fallback deserves more explanation.

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%, so the baseline is 3. The description adds only the read/index-only restriction on `call` and the schema-return notion; it contributes nothing on `query`, `limit`, or `enable` beyond what the schema already says.

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

Purpose4/5

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

The description names a specific verb set and resource — 'Discover or enable experts and return their schemas' — so an agent knows this tool both lists and activates tools and returns schema payloads. It does not, however, differentiate itself from siblings like status, search, skeleton, or explain, and the term 'experts' is never grounded in the sibling catalog.

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

Usage Guidelines3/5

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

One conditional is spelled out: if the client cannot refresh its catalog, use the `call` parameter to invoke a supported read/index tool. That is real when-to-use guidance for one path, but there is no guidance on when to discover versus enable, how to choose `query` values, or when to prefer a sibling tool over this one.

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