Skip to main content
Glama

sii_descargar_oficio

Read-only

Download the PDF of an SII administrative ruling by providing its office number and publication date, with an optional year index and save destination.

Instructions

Descarga el PDF de un oficio de la jurisprudencia administrativa del SII, identificándolo por su número y su fecha de publicación.

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": {
      "numero": "<numero>",
      "fecha": "<fecha>"
    },
    "name": "sii_descargar_oficio"
  }
}

Input Schema

NameRequiredDescriptionDefault
anioNoAño del índice a consultar (por defecto, el año en curso)
fechaYesFecha de publicación del oficio, formato dd/mm/aaaa
numeroYesNúmero del oficio tal como aparece en el listado (p. ej. 2407 o 0358)
destinoNoRuta donde guardar el PDF (opcional: si se omite, queda en la caché y se informa la ruta)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.14.0
    • changedInput schema / properties / destino / description
      Previous value: -"Ruta donde guardar el PDF (opcional: si se omite, sólo se informa el tamaño descargado)"New value: +"Ruta donde guardar el PDF (opcional: si se omite, queda en la caché y se informa la ruta)"
  2. Addedv1.5.11

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds that the operation downloads a PDF, but does not disclose error behavior, rate limits, or return details beyond what the schema's 'destino' parameter already explains.

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 clear sentence with the action and resource front-loaded. No filler or redundant wording.

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 download tool with full schema coverage and annotations, the description is nearly complete. It could mention what is returned when successful, though the schema's 'destino' description partly covers that.

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%, so all four parameters are documented. The description restates the two required identifiers (número and fecha de publicación) but adds no syntax, format, or behavioral meaning beyond the schema.

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?

Specific verb 'Descarga' plus precise resource 'PDF de un oficio de la jurisprudencia administrativa del SII', identified by number and publication date. Clear, though it does not name sibling tools or explicitly distinguish itself from tools like sii_leer_documento.

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 implied by the requirement to identify the oficio by number and publication date, but there is no explicit when-to-use guidance, no mention of alternatives, and no exclusions or prerequisites.

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