Skip to main content
Glama

consultar_fraccion

Find a Mexican TIGIE tariff fraction by 8-digit code, NICO, or short description; returns IGI, IVA, IEPS, regulations, NICO codes, 2026 changes, database date, and record link.

Instructions

Consulta una fracción arancelaria de México (TIGIE/LIGIE): IGI, IVA, IEPS, regulaciones, NICO y cambio 2026 documentado, con la fecha de la base y el enlace a su ficha. Una fracción por llamada. No clasifica ni calcula impuestos a pagar.

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": {
      "consulta": "<consulta>"
    },
    "name": "consultar_fraccion"
  }
}

Input Schema

NameRequiredDescriptionDefault
consultaYesFracción de 8 dígitos (con o sin puntos), NICO de 10, o descripción corta.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does meaningful work: it discloses the provenance fields (base date, ficha link), that the 2026 change is documented, the one-identifier-per-call constraint, and a clear negative boundary. It does not state read-only character, auth needs, or what happens when a fraction is not found, so it stops short of fully covering behavior.

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?

Three short sentences, front-loaded with the resource and its contents, followed by the invocation constraint and then the exclusion. Nothing is redundant with the title or restates the name.

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?

No output schema exists, so naming the returned fields (IGI, IVA, IEPS, regulaciones, NICO, fecha de base, enlace) plus the documented 2026 change is exactly what an agent needs to decide whether this call answers its question. Combined with the single-parameter schema and the explicit exclusion, the definition is complete for its complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already defines the accepted formats (8 digits with or without dots, 10-digit NICO, or short description) and the 80-char cap. The description still adds semantics beyond the schema by stressing a single fraction per call, implying the parameter is a scalar lookup key rather than a list or batch input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (consulta/retrieves) and specific resource (fracción arancelaria de México, TIGIE/LIGIE), then enumerates exactly what comes back: IGI, IVA, IEPS, regulaciones, NICO, cambio 2026, fecha de la base and link to the ficha. An agent knows precisely what this tool yields without opening any other field.

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?

'Una fracción por llamada' tells the agent to call once per identifier rather than batching, and 'No clasifica ni calcula impuestos a pagar' explicitly scopes out classification and tax computation, which is the most likely wrong expectation. No alternative tool is named, but the sibling list is empty, so there is nothing to route away from.

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