Skip to main content
Glama

sii_leer_documento

Read-only

Retrieve the full text of SII circulars, resolutions, or oficios by type and number for accurate citations, since index summaries are not citable. Extracted from official PDFs and cached.

Instructions

Devuelve el texto íntegro de una circular, resolución exenta u oficio del SII, extraído del PDF oficial (queda guardado en la caché junto a un .txt). Úsalo para citar: la materia del índice es sólo un resumen.

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": {
      "tipo": "<tipo>",
      "numero": "<numero>"
    },
    "name": "sii_leer_documento"
  }
}

Input Schema

NameRequiredDescriptionDefault
anioNoAño de publicación (por defecto, el año en curso)
tipoYesClase de documento
fechaNoFecha dd/mm/aaaa; necesaria si en ese año hay dos oficios con el mismo número (Renta, IVA y Otras normas numeran por separado)
numeroYesNúmero del documento (p. ej. 50, 115 o 1873)
max_caracteresNoTope de caracteres del texto devuelto (por defecto 60000; el .txt guarda el texto completo)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, yet the description adds genuinely useful behavioral context beyond them: the text is extracted from the official PDF and cached on disk alongside a .txt file, and the index subject line is only a summary. It does not explain failure behavior when a document is not found or what happens on a cache hit, so it is not fully transparent.

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 sentences with no filler: the first delivers what is returned and its provenance plus the caching side effect, the second delivers the intended use. The most decision-relevant information (full text, official PDF) is front-loaded.

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 five-parameter read tool with full schema coverage and annotations covering the safety profile, the description covers provenance, caching, truncation context (via the schema) and intended use. It leaves out error/not-found behavior and whether the cached .txt can be re-read, which are minor given the rest of the definition.

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%, so every parameter (anio, tipo, fecha, numero, max_caracteres) is already documented in the schema. The description only echoes the document classes covered by the tipo enum and does not add format, disambiguation or edge-case guidance beyond the schema, which is the expected baseline.

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 concrete verb and resource: returns the full text of a circular, resolución exenta or oficio from the SII, extracted from the official PDF. It implicitly separates itself from the index/summary view by warning that 'la materia del índice es sólo un resumen', so an agent can tell this is the full-text retrieval step rather than a search step. It does not name a specific sibling tool, which keeps it short of a 5.

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?

'Úsalo para citar' gives an explicit use case (citation/exact quoting) and the trailing clause explains why the index summary is insufficient for that. There is no explicit when-not or named alternative for locating a document in the first place, so the routing guidance is clear but not complete.

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