Skip to main content
Glama

descubrir_herramientas

Read-only

Dynamically search available MCP legal tools and return only relevant matches with their input schemas on demand, reducing context token usage for Chilean legal research tasks.

Instructions

Búsqueda dinámica de herramientas MCP (perfil router / Tool Search): usa LegalOpenJev (<5 ms) y ranking léxico para devolver solo las herramientas relevantes y su inputSchema bajo demanda, reduciendo ~85 % el consumo de tokens de contexto.

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": {
      "consulta": "<consulta>"
    },
    "name": "descubrir_herramientas"
  }
}

Input Schema

NameRequiredDescriptionDefault
limiteNoMáximo de herramientas sugeridas (por defecto 6)
consultaYesDescripción de la tarea jurídica o palabra clave (ej. 'estudio de títulos CBR', 'sanción SMA ruido', 'comparar versiones ley')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that: sub-5 ms latency, lexical ranking as the retrieval mechanism, that only relevant tools and their inputSchema come back, and an ~85% context-token reduction. What is missing is any note on result limits or truncation behavior beyond the 'limite' parameter.

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?

A single dense sentence that front-loads the purpose and the mechanism before the benefit. Every clause contributes (profile, engine, ranking, return shape, token savings), though the parenthetical jargon ('perfil router / Tool Search') adds slight clutter.

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 two-parameter read-only discovery tool with no output schema, the definition covers what it does, how it ranks, and what it returns, which is what an agent needs to invoke it correctly. It could be stronger by stating explicitly that this is about finding tools rather than legal sources, given the dense sibling namespace.

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 both parameters carry their own descriptions including an example query, so the schema does the heavy lifting. The description adds no syntax, phrasing, or language guidance for 'consulta' beyond confirming that relevant tools are returned. Baseline 3 is appropriate.

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 operation (dynamic MCP tool search via a router/Tool Search profile) and states the effect: returning only relevant tools plus their inputSchema on demand, with a token-saving rationale. That is far more than a restatement of the name. It stops short of a top score because it never distinguishes itself from plausible siblings such as busqueda_universal or agent_list, leaving the agent to infer that this one searches tools rather than legal content.

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?

Usage is only implied by the phrase 'bajo demanda' — the agent can gather it should be called when it needs to discover tools rather than fetch documents. There is no explicit when-to-use, when-not-to-use, or named alternative, and no statement about whether it should precede other discovery tools. Adequate but clearly gapped.

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

Deploy Server

Other Tools