Skip to main content
Glama

Avanciq - tax rates, codes, e-invoices, calculation checks

Was this tax/e-invoice code valid on a date?

code_check
Read-onlyIdempotent

1 call per code. Checks whether an official code-list entry was in force on a date, from the authorities' own published files: Brazil NF-e (NCM, CFOP, cClassTrib, CST, CSOSN...), Mexico SAT CFDI 4.0 and 3.3 catalogs (c_UsoCFDI, c_ClaveProdServ, c_RegimenFiscal...), Poland KSeF FA(2)/FA(3) lists (TStawkaPodatku, TKodKraju, TGTU...). Answers status valid / expired / not_yet_valid / never_existed / not_covered with valid_from/valid_to, table version, source file link and receipt id. Use before accepting a code on an invoice or when checking an old one. Send either one check (country, table, code, date) or 'checks' (list, max 100).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "code_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoThe code as written on the invoice; dots and spaces are ignored (8471.30.12 = 84713012).
dateNoThe date that matters (issue date) as YYYY-MM-DD.
tableNoOfficial table name, e.g. ncm, cfop, cclasstrib, cst_icms (BR); c_UsoCFDI, c_ClaveProdServ, c_RegimenFiscal, c_ClaveUnidad (MX, add @3.3 for the CFDI 3.3 catalog); TStawkaPodatku, TKodKraju, TKodWaluty, TGTU (PL). Call coverage for the full list.
checksNoOptional batch instead of the single fields: list of {country, table, code, date}.
countryNobr, mx or pl.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds important operational details beyond that: one call per code, batch limit of 100, the exact status vocabulary, and returned metadata such as valid_from/valid_to, table version, source file link, and receipt id.

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 description is front-loaded with the core action and the per-code calling constraint, followed by coverage, return values, usage guidance, and batching. It is dense but each sentence carries relevant information; the long parenthetical table examples are useful but slightly heavy.

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?

There is no output schema, so the description carries the burden of explaining results, and it does: it names possible statuses, returned fields, table version, source link, and receipt id. Combined with schema-level parameter documentation, an agent has enough to invoke the tool correctly.

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%, so the baseline is 3. The description still adds meaning by clarifying the two calling modes (single fields vs. 'checks' list) and by giving representative table names across all three countries, helping an agent choose the correct table parameter.

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?

The title and description state a specific verb and resource: checking whether an official code-list entry was in force on a given date, across named Brazil, Mexico, and Poland registries. It is distinguishable from siblings like coverage and einvoice_check because it is scoped to a single-code validity lookup with explicit statuses.

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?

The description gives clear usage context: 'Use before accepting a code on an invoice or when checking an old one,' and explains the batch alternative via 'checks' up to 100. It does not explicitly exclude or compare with siblings such as einvoice_check, so it falls short of a 5.

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