Skip to main content
Glama

TributaSoft · Documentación oficial

Buscar en la documentación

buscar
Read-onlyIdempotent

Busca en los instructivos, tutoriales y preguntas frecuentes de TributaSoft. Devuelve hasta 8 resultados con título, resumen y enlace.

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

Input Schema

NameRequiredDescriptionDefault
consultaYesQué necesita hacer el usuario, en español. Ej.: «emitir una nota de crédito».

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the description's added value is the result-shape disclosure: a cap of 8 results, each with título, resumen y enlace. That is genuinely useful for planning. It stops short of ranking/ordering behavior or what happens when nothing matches.

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 short sentences, zero filler, and the scope of the corpus is front-loaded ahead of the return-value detail. Every clause carries information an agent can use.

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 simple single-parameter read tool with full annotation coverage and a fully documented schema, the description covers corpus, result cap and returned fields, which is enough to call it and interpret the response. Minor gaps remain around result ordering and the empty-result case, but nothing essential 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?

There is only one parameter and schema coverage is 100%, with the schema itself explaining that 'consulta' is what the user needs to do, in Spanish, with an example. The description adds no meaning beyond that, so the baseline 3 applies.

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?

States a specific verb (busca) and the exact corpus it searches: instructivos, tutoriales y preguntas frecuentes de TributaSoft. That distinguishes it in spirit from the sibling readers/listers, but it never names them, so the differentiation is implied rather than explicit.

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: 'busca' versus sibling names like leer_instructivo/leer_pregunta suggests search-then-read, but the description gives no when-to-use rule, no exclusion, and no pointer to the follow-up tool for opening a result. An agent must infer the workflow.

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