Skip to main content
Glama

Progressive T-Zero MCP Tool Discovery Catalog

search_tools
Read-onlyIdempotent

Discover and search registered T-Zero tools by keyword or domain category, returning ranked matches to find relevant capabilities without loading every schema at once.

Instructions

Progressively discover and search registered T-Zero tools by keyword or domain category rather than loading all 58 schemas at once (unlike codebase searches; use 'search_codebase' for searching repository source files instead).

Parameters:

  • query: Optional keyword query (e.g., 'secret audit', 'pagerank', 'diff', 'merge').

  • category: Domain filter (all, context, security, ast, memory, swarm, design).

  • limit: Maximum tool entries returned (integer 1-30; defaults to 10).

Behavior:

  • Mutability & Speed: Read-only, idempotent catalog lookup executing in <5ms.

  • Auth & Boundaries: Zero authentication, external credentials, or network access required.

Usage Guidelines:

  • When to use: Discover specialized AST, Jarvis, or security tools by keyword; availability varies by tool mode.

  • When NOT to use: Do not use when searching source files or symbols inside the workspace repository — use 'search_codebase' instead.

Returns: Structured dictionary with query, total_available, and ranked tools (name, category, summary).

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
limitNoMaximum number of matching tools to return (1-30).
queryNoKeyword query (e.g., 'secret audit', 'pagerank', 'diff', 'merge').
categoryNoOptional category filter: 'all', 'context', 'security', 'ast', 'memory', 'swarm', 'design'.all

Output Schema

NameRequiredDescriptionDefault
queryYes
toolsYes
total_availableYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv11.12.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description adds genuinely new facts: sub-5ms execution, zero auth/credentials/network, and the '58 schemas' framing that motivates progressive discovery. It stops short of explaining how results are ranked or what happens when zero matches are found, which keeps it off a 5.

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?

The lead sentence is front-loaded with the core distinction and the rest is broken into scannable labeled sections. It loses a point for duplication: the search_codebase exclusion appears twice (opening sentence and 'When NOT to use'), and the parameter block largely mirrors the schema.

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

Completeness5/5

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

For a three-parameter, zero-required read-only discovery tool, nothing an agent needs is missing: purpose, exclusions, cost, auth boundaries, and the return shape are all stated. An output schema exists, so the brief returns note is sufficient rather than a gap.

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 schema already documents query, category, and limit including the default of 10 and the 1-30 range. The description restates the same parameters with illustrative keywords, which aids intuition but adds no constraints or edge-case semantics beyond the schema — the baseline 3 for a fully documented schema.

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?

The opening sentence gives a specific verb ('progressively discover and search') and a specific resource ('registered T-Zero tools') scoped by 'keyword or domain category'. It also names the sibling it is not — 'use search_codebase for searching repository source files instead' — so an agent can route correctly without opening either 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?

Explicit sections for 'When to use' (discover AST, Jarvis, or security tools by keyword) and 'When NOT to use' (searching source files or symbols — use search_codebase). The alternative is named with the condition that selects it, and the caveat that availability varies by tool mode sets realistic expectations.

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