Skip to main content
Glama

Validate Costa Rica cédula (tax ID, beta)

validate_costa_rica_cedula
Read-onlyIdempotent

Check a Costa Rican tax ID (cédula física, cédula jurídica, DIMEX or NITE) live against the Ministerio de Hacienda's public taxpayer lookup. Returns the ID type, taxpayer status (registered or not), tax regime, delinquent (moroso) and non-filer (omiso) flags, tax administration office, registered economic activities and a pass/review/fail assessment with reasons. Beta: the Hacienda endpoint is not formally documented. Names are returned only for legal entities; for individuals the name is withheld.

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": {
      "cedula": "<cedula>"
    },
    "name": "validate_costa_rica_cedula"
  }
}

Input Schema

NameRequiredDescriptionDefault
cedulaYesCosta Rican ID: 9 digits (cédula física), 10 digits (cédula jurídica or NITE) or 11-12 digits (DIMEX), e.g. "2-100-042005". Dashes are ignored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / cedula / description
      Previous value: -"Costa Rican ID: 9 digits (cédula física), 10 digits (cédula jurídica or NITE) or 11-12 digits (DIMEX), e.g. \"3-101-005744\". Dashes are ignored."New value: +"Costa Rican ID: 9 digits (cédula física), 10 digits (cédula jurídica or NITE) or 11-12 digits (DIMEX), e.g. \"2-100-042005\". Dashes are ignored."
  2. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, and the description still adds substantial context: the beta status and undocumented endpoint (implying possible instability), the exact set of returned fields including moroso/omiso flags, and the privacy caveat that names are withheld for individuals. That privacy and reliability disclosure cannot be derived from any structured field.

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?

The purpose and lookup target are front-loaded in the first sentence, followed by the return-value summary and then the beta/privacy caveats. It is dense but each sentence carries real information; the long enumeration of returned fields is justified because there is no output schema.

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?

With no output schema, the description compensates by enumerating the response shape (ID type, status, regime, moroso/omiso flags, activities, pass/review/fail assessment). Combined with the beta caveat and the name-withholding rule, an agent has everything needed to call it and interpret the result.

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?

There is a single parameter with 100% schema description coverage, including digit-count rules per ID type and an example plus the 'dashes are ignored' note. The description adds nothing beyond that about the cédule argument, so the baseline of 3 applies — the schema does all the work here.

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?

The description states a specific verb ('Check') and resource (a Costa Rican tax ID) plus the exact scope: a live lookup against the Ministerio de Hacienda's public taxpayer lookup, covering the four ID subtypes. The word 'live' implicitly separates it from format-only siblings like validate_tax_id_format, but no sibling is named explicitly, so it stops just short of full differentiation.

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 clearly implied by 'live against the Ministerio de Hacienda's public taxpayer lookup', so an agent can infer this is the real-lookup path rather than a syntax check. However, there is no explicit when-to-use versus validate_tax_id or validate_tax_id_format, and no stated preconditions (e.g., rate limits, network dependency) or exclusions.

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