Skip to main content
Glama

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

What Avanciq covers (free)

coverage
Read-onlyIdempotent

Free (0 calls). Lists what the other tools can answer: VAT/GST jurisdictions, official code tables per country with dates, e-invoice rulesets, and the calculation kinds with their exact input fields. Call it once when unsure whether something is covered or which input fields verify_calculation needs.

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": "coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, non-destructive, idempotent, closed-world), so the description's contribution is the cost/usage model: 'Free (0 calls)' and the 'call it once' cadence, which is behavior an agent cannot read off the annotations. It stops short of describing the response shape or how much detail each listed section carries.

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 tight clauses: cost, contents, and when to call. The content enumeration is front-loaded and every sentence earns its place, with no filler or restated title.

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 no-argument discovery tool with an explicit contents list and call trigger, almost everything an agent needs is present. A brief note on the output structure (e.g. that it returns sectioned lists of countries/rulesets) would make it fully self-sufficient since no output schema exists.

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?

Zero-parameter tool, so the baseline is 4; the description adds that no input is required beyond noting the free call cost. Nothing about parameters is missing because there are none.

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 (lists) and resource (coverage catalogue: jurisdictions, code tables, e-invoice rulesets, calculation kinds and their input fields). It also distinguishes itself from siblings by positioning itself as the discovery tool that precedes verify_calculation and the check tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('when unsure whether something is covered or which input fields verify_calculation needs') plus a usage constraint ('call it once'), and names the sibling whose inputs it resolves. The when-to-use condition is concrete rather than implied.

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