Skip to main content
Glama

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

Artigo do RITI

artigo_riti
Read-only

Devolve o texto em vigor de um artigo do Regime do IVA nas Transações Intracomunitárias (RITI), 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.

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_riti"
  }
}

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.6/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 that only the text 'em vigor' is returned (no historical versions), that a link to iva.pt is included, that the source is the Autoridade Tributária, and that the English text is an unofficial translation. It does not say how a missing/invalid article is reported, which is the remaining gap.

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?

Two short sentences, front-loaded with what is returned, then the source and the language variant. No filler, though 'Fonte: Autoridade Tributária e Aduaneira' is of marginal decision value.

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?

A simple two-parameter read tool with full schema coverage, an enum, and a readOnly annotation. The description adds the in-force scope, the returned link, the source, and the unofficial-translation caveat — everything an agent needs to call it correctly.

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%, including an enum and an example of the artigo format ('36', '7-A', 'listas'), so the schema carries the semantics. The description only restates the idioma=en option, adding no format or edge-case detail beyond the schema — baseline 3.

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: 'Devolve o texto em vigor de um artigo do Regime do IVA nas Transações Intracomunitárias (RITI)'. The RITI acronym plainly distinguishes it from sibling artigo_civa (CIVA) and from pesquisar_legislacao/validar_iva, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

The description never says when to pick this tool over artigo_civa or pesquisar_legislacao, nor any preconditions (e.g. what happens if the article number doesn't exist). The only guidance is the idioma=en tip, which is parameter-level rather than tool-selection guidance.

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