Skip to main content
Glama

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

Explain an EN 16931 rule (free)

einvoice_rule
Read-onlyIdempotent

Free (0 calls). Official text and fix hint for one EN 16931 business rule id, e.g. BR-CO-15, so you can explain a rejection.

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": {
      "rule_id": "<rule_id>"
    },
    "name": "einvoice_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
rule_idYesRule id like BR-CO-15, BR-S-08, BR-01.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered elsewhere. The description still adds useful context: the call is free (0 calls) and the response contains official text plus a fix hint, which matters since no output schema exists. It does not say what happens for an unknown rule 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?

One tight sentence with zero filler; every clause carries information. Leading with the pricing tag before the purpose is slightly less front-loaded than ideal, but the whole entry is short enough that it costs nothing.

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 lookup tool with full schema coverage and no output schema, the description covers what comes back (official text and fix hint) and the cost model. Only the edge-case behavior for invalid rule ids is left unspecified.

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 there is a single well-documented parameter, so the schema does the heavy lifting. The description only restates the parameter with an inline example, adding marginal 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?

States a specific verb and resource: returns the official text and fix hint for one EN 16931 business rule id, with a concrete example (BR-CO-15). The purpose is unambiguous, though it never explicitly distinguishes itself from einvoice_check or verify_calculation.

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 clause "so you can explain a rejection" implies the usage context (post-rejection explanation) and "Free (0 calls)" tells the agent the cost. There is no explicit when-not guidance or named alternative for looking up rules versus validating an invoice.

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