Skip to main content
Glama

iva.pt — EU VAT check (VIES) and Portuguese VAT law

Artigo do Código do IVA

artigo_civa
Read-only

Devolve o texto em vigor de um artigo do Código do IVA português (CIVA), com a ligação para iva.pt. Fonte: Autoridade Tributária e Aduaneira. Também em inglês (tradução não oficial) com idioma=en. Portuguese VAT Code article, optionally in English.

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": {
      "artigo": "<artigo>"
    },
    "name": "artigo_civa"
  }
}

Input Schema

NameRequiredDescriptionDefault
artigoYesNúmero do artigo, por exemplo "36", "7-A" ou "listas" (listas anexas).
idiomaNopt: texto oficial (predefinição); en: tradução inglesa não oficial.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the text returned is the version 'em vigor' (currently in force), the authoritative source is the Autoridade Tributária e Aduaneira, a link to iva.pt comes with the result, and the English version is flagged as an unofficial translation — a trust caveat an agent would otherwise not know.

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 core statement, source, and language option are front-loaded in the first two Portuguese sentences with no filler. The trailing English sentence largely restates what was already said (the English option), which is mild redundancy, though it reasonably serves an English-reading agent.

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?

With only two parameters, full schema coverage, and no output schema, the description carries its share: it states what is returned (the article text plus the iva.pt link), the authority of the source, and the caveat on the English translation. Only an indication of behavior for an invalid or non-existent article number is missing, which keeps it just short of complete.

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 description coverage is 100%, including the example article formats and the pt/en enum semantics, so the baseline is 3. The description repeats the idioma=en option and its unofficial nature but adds no format, normalization, or error-handling detail beyond what the schema already states.

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 names a specific verb and resource: it returns the in-force text of an article of the Portuguese VAT Code (CIVA), with a link to iva.pt. That is far more precise than the title alone and implicitly separates it from siblings like artigo_riti (a different code) and pesquisar_legislacao (search). However, it never explicitly distinguishes itself from those siblings, which is what a 5 would require.

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 only implied: an agent can infer this is the tool for fetching a known CIVA article by number, and the 'idioma=en' note hints at the translation variant. There is no explicit statement of when to prefer this over pesquisar_legislacao (when you don't know the article number) or artigo_riti (a different statute), nor any stated prerequisite or exclusion.

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