Ecuafact API · Documentación

leer_guia

Read-onlyIdempotent

Devuelve una guia en Markdown. Con seccion, devuelve solo la seccion cuyo titulo coincide; las guias largas (por ejemplo las de SDK) conviene leerlas por seccion.

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": {
      "slug": "<slug>"
    },
    "name": "leer_guia"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Slug de la guia, por ejemplo 'emision-01' o 'webhooks'. Tambien acepta su URL.
`seccion`	No	Titulo o parte del titulo de una seccion (opcional), por ejemplo 'Firma' o 'Catalogo de codEstado'.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedInput schema / properties / seccion / description

Previous value: -"Titulo o parte del titulo de una seccion (opcional), por ejemplo 'Firma' o 'Catalogo de codigos'."New value: +"Titulo o parte del titulo de una seccion (opcional), por ejemplo 'Firma' o 'Catalogo de codEstado'."

First observedOct 20, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent and closed-world behavior, so safety is covered. The description adds that output is Markdown and that a section match is by title, but it does not say what happens when the slug is unknown or no section title matches, which is the main remaining behavioral gap for a read tool.

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?

Two sentences, purpose first, usage second, no filler. The second clause about section matching overlaps somewhat with the schema description, but the text is appropriately sized for a simple read tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with full schema coverage and safety annotations, this is close to sufficient and it even discloses the Markdown return format in the absence of an output schema. It still omits error/empty-match behavior and slug discovery paths, which an agent may need.

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 coverage is 100% and both parameters are documented with examples, including that slug also accepts a URL, so the schema does the heavy lifting. The description only restates the section-filtering behavior already implied by the 'seccion' parameter and adds rationale rather than new semantics.

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 una guia en Markdown') plus a second mode (section-only retrieval). It does not name a sibling such as listar_guias or buscar_documentacion, so differentiation is left to inference, but the operation itself is unambiguous.

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 a clear conditional recommendation: for long guides such as SDK docs, read them by section rather than whole. It stops short of naming alternatives or stating when not to use this tool (e.g. discovering guide slugs should go to listar_guias).

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

All Ecuafact API · Documentación tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?