Skip to main content
Glama

Buscar herramienta en el catálogo

find_tool
Read-onlyIdempotent

Busca entre las 502 herramientas de este servidor por palabras clave (español o inglés) y una familia opcional, y devuelve las mejores coincidencias con sus esquemas de entrada. Cuándo: aún no se sabe qué herramienta sirve para una tarea. No para: ejecutar una herramienta (eso lo hace tools/call). Efectos secundarios: ninguno. Determinista. Límites: consulta de hasta 200 caracteres, hasta 25 resultados.

EN: Searches the 502 tools of this server by keywords (English or Spanish) and an optional family, and returns the best matches with their input schemas. When: the right tool for a task is not known yet. Not for: running a tool (tools/call does that). Side effects: none (read-only, no network access, no stored state). Deterministic: the same query gives the same results. Limits: query up to 200 characters, up to 25 results.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
queryYesKeywords, e.g. "sha256", "festivos colombia", "uuid v7"
familyNoOptional family filter

Output Schema

NameRequiredDescriptionDefault
resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, openWorldHint=false and destructiveHint=false, so the description's 'side effects: none / deterministic' restates part of that. It does add meaning beyond the annotations by naming the concrete constraints (query up to 200 chars, up to 25 results) and stating that no network access or stored state is involved, which tells the agent this call is free to retry and safe to spam during exploration.

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 When / Not for / Side effects / Deterministic / Limits — a clean, scannable structure. The cost is that the entire block is duplicated in Spanish and English, roughly doubling length with no new information; the bilingual mirroring is defensible for this catalogue but is the main reason it is not a 5.

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 3-parameter discovery tool with an output schema already declared, this covers everything an agent needs: what it returns (matches with their input schemas), when to call it, what it is not for, safety profile, and hard limits. No gaps remain that would cause a misinvocation.

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 enum, maxLength 200 and maximum 25 are already encoded in the input schema, so the description's 'hasta 200 caracteres, hasta 25 resultados' is largely a restatement. The one genuinely additive detail is that keywords may be in Spanish or English, which tells the agent it can query bilingually — useful but marginal over the 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?

Opens with a specific verb+resource+scope: searches the 502 tools of this server by keywords plus an optional family and returns best matches with their input schemas. It explicitly differentiates itself from tools/call, so an agent scanning a 400+ tool catalogue knows instantly that this is the discovery entry point rather than an executor.

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 an explicit trigger ('Cuándo: aún no se sabe qué herramienta sirve para una tarea') and an explicit exclusion with the alternative named ('No para: ejecutar una herramienta (eso lo hace tools/call)'). Nothing about when to reach for this versus a direct sibling call is left to inference.

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