Skip to main content
Glama

TributaSoft · Documentación oficial

Leer una pregunta frecuente

leer_pregunta
Read-onlyIdempotent

Devuelve la respuesta completa de una pregunta frecuente por su id (el que aparece en los resultados de «buscar» con tipo faq).

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": {
      "id": "<id>"
    },
    "name": "leer_pregunta"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId de la pregunta, p. ej. «prueba-gratis-300-documentos».

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and side-effect behavior are covered. The description adds value beyond them by stating the return payload is the complete answer (as opposed to the snippet shown in search results) and by tying the id to a specific discovery path. It does not describe behavior for an unknown id, a minor gap.

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?

A single sentence that front-loads the operation and return value, with the id provenance in a parenthetical that earns its place. No filler or restated name/title.

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 one-parameter read tool with full annotation coverage and no output schema, the definition supplies the operation, the key's origin, and the shape of the return (complete answer). Only edge-case behavior such as an unknown id is left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter at 100% schema coverage, so the schema already documents the id pattern and format. The description still adds meaning by explaining the id originates from «buscar» results of type faq, which is provenance the schema cannot express.

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?

Names a specific verb and resource ("Devuelve la respuesta completa de una pregunta frecuente") plus the lookup key ("por su id"), and the "tipo faq" qualifier partly separates it from the instructivo siblings. It never states explicitly that it is not the tool for reading instructivos, so full sibling differentiation is implied rather than stated.

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

Usage Guidelines4/5

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

Gives clear usage context: the id is the one returned by «buscar» for results of type faq, which tells an agent exactly when this tool applies and where to get the input. It does not spell out a when-not case or name leer_instructivo as the alternative for non-faq content.

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