Skip to main content
Glama

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

Pesquisar no CIVA e no RITI

pesquisar_legislacao
Read-only

Pesquisa por palavras (em português) nos títulos e no texto dos artigos do Código do IVA e do RITI. Devolve os artigos mais relevantes com ligação. Use depois artigo_civa ou artigo_riti para ler o texto.

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": {
      "pesquisa": "<pesquisa>"
    },
    "name": "pesquisar_legislacao"
  }
}

Input Schema

NameRequiredDescriptionDefault
diplomaNoOpcional: limitar a um diploma.
pesquisaYesPalavras a procurar, por exemplo "declaração recapitulativa" ou "autoliquidação".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

readOnlyHint already tells the agent this is a safe read. The description adds behavior beyond the annotation: search is keyword-based, Portuguese-only, covers both titles and article body text, and returns a relevance-ranked set with links – more than the annotation provides.

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?

Two sentences, zero filler, with the core behavior first and the follow-up routing second. Every clause earns its place.

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 two-parameter read-only search with no output schema, the description covers enough: what is searched, what comes back (relevant articles with links), and what to do next. Only minor gaps remain, such as result ordering or result-count behavior.

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 the enum for diploma is documented, so the schema already carries the parameter burden. The description only adds the Portuguese-language constraint on the query, which is marginal extra value.

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 (pesquisar por palavras) plus the exact resources and fields searched (títulos e texto dos artigos do Código do IVA e do RITI), and it distinguishes itself from artigo_civa/artigo_riti by framing itself as the lookup step rather than the reading step.

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?

It explicitly routes the agent onward: 'Use depois artigo_civa ou artigo_riti para ler o texto', which is exactly the workflow an agent needs. It lacks an explicit negative case (e.g., when to skip search), but the context is unambiguous.

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