Skip to main content
Glama

TributaSoft · Documentación oficial

Leer un instructivo paso a paso

leer_instructivo
Read-onlyIdempotent

Devuelve un instructivo completo: ruta en el sistema, pasos, notas, video y PDF. Use el id que da «buscar» o «listar_instructivos» (p. ej. 03.6).

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_instructivo"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId del instructivo, p. ej. «03.6».

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), and the description adds genuinely new behavioral information by listing the returned components (path, steps, notes, video, PDF). It does not say how it behaves with an invalid or non-existent id, which is the remaining 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?

Two short sentences, front-loaded with the return payload and followed by the single operational constraint. Nothing is padding; every clause carries information an agent needs.

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 one-parameter read-only tool with no output schema, the description fills the important hole by enumerating what the response contains and where the id originates. Nothing essential for a correct call is missing.

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?

Schema description coverage is 100%, so the baseline is 3; the description earns an extra point by adding provenance semantics — the id is not free-form but comes from buscar or listar_instructivos. The inline example «03.6» merely repeats the schema and adds nothing.

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 and resource ("Devuelve un instructivo completo") and enumerates the payload (ruta en el sistema, pasos, notas, video y PDF), so the agent knows exactly what it gets. It separates itself from buscar and listar_instructivos by naming them as the source of the id, though it never explicitly says what it is not.

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 workflow context: the id must come from «buscar» or «listar_instructivos», which tells the agent to call those first. It stops short of exclusion rules (e.g., what to do when the id is unknown or when a summary is enough instead of the full document).

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