Skip to main content
Glama
mcp-hacienda-cr

mcp-hacienda-cr

by jmnzcn

Consultar exoneración

consultar_exoneracion
Read-only

Retrieves Costa Rica tax exemption details by authorization number, including beneficiary, percentage, validity dates, and covered CABYS codes.

Instructions

Datos de una exoneración de impuestos registrada en Hacienda a partir de su número de autorización: beneficiario, porcentaje, vigencia y códigos CABYS que cubre.

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": {
      "autorizacion": "<autorizacion>"
    },
    "name": "consultar_exoneracion"
  }
}

Input Schema

NameRequiredDescriptionDefault
autorizacionYesNúmero de documento de la exoneración. Ej: "AL-00020402-24".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 and openWorldHint=true, so the safety profile is covered. The description usefully discloses that data comes from an external Hacienda registry and enumerates the returned fields. It says nothing about behavior when the authorization number is invalid or not found, which matters for an external lookup.

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?

One dense sentence that front-loads the resource and key, then lists the returned fields. No filler or redundant restatement of the schema.

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-only lookup with annotations present and no output schema, the description covers source, key, and return fields, which is most of what an agent needs. The only gap is failure/not-found behavior.

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 the single parameter already carries a format example ("AL-00020402-24"). The description restates that the input is the authorization number but adds no format, validation, or normalization detail beyond the schema, so baseline 3 applies.

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 the specific resource (exoneración de impuestos registered at Hacienda), the lookup key (número de autorización), and the fields returned (beneficiario, porcentaje, vigencia, CABYS). It is clearly distinguishable from siblings such as consultar_contribuyente or buscar_cabys. It stops short of a clean verb-led statement of operation, relying on the title for the 'consultar' action.

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?

The description implies when to use it (when you have an authorization number and need exoneration details), and the 'a partir de su número de autorización' phrase anchors the input. It gives no explicit when-not-to-use guidance or pointers to alternatives like buscar_cabys when only CABYS coverage is needed.

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