Skip to main content
Glama

VeriActa: law in force, by country

law_lookup
Read-onlyIdempotent

Official legislation of a country as in force on a date: the provisions that answer a question, in full, with their citation and source. Call it before every answer that rests on a provision (a rate, a threshold, a deadline, a duty, a definition), and again for each follow-up question or new fact; do not reuse an earlier result for a new point. Write the query in the country's language and in the words of the statute, covering every element of the question, and name the act in act when you know it. Your own knowledge of the likely article or wording is a good search lead, but take every figure from the returned text. Read warnings and any status, freshness_warning or act_match before answering: they say when the act was not confirmed, when a published amendment changes the wording, and what to check. If the result does not answer the question, say the legal basis was not confirmed. Each country's own rules for asking are in jurisdictions.

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": {
      "jurisdiction": "<jurisdiction>"
    },
    "name": "law_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
actNoThe act, when you can tell which one: its name, common abbreviation, official number or id ("ustawa o VAT", "LIVA", "Ley 35/2006", "VAT Directive", "UStG"). A named act is answered better than an open question. Do not guess.
urlNoOnly an exact link to the official text that the user gave. Never construct one.
pathNoOne provision to read: the path a search returned or a citation ("art. 113 ust. 1", "artículo 91.Uno", "Article 98(2)", "§ 12 Abs. 2 Nr. 1").
as_ofNoThe day the wording must be in force on, YYYY-MM-DD. Today when left out.
limitNoHow many results a search returns, where the country supports it.
queryNoWhat to find, in the country's language and in the words of the statute. Cover every element of the question (rates, thresholds, how a base is computed), not just the topic's name. Required for a search.
actionNosearch (default): provisions that answer the query. provision: the text at `path`. act: an act's data and outline. resolve: identify an act by name. compare (jurisdiction EU): the EU provision at `act` + `path` next to the national provisions that carry it in the countries of `compare_with`. The country's notes say which it supports.
interpretNoDefault false: return the provisions. true only where the country supports applying the law to the facts in the query.
compare_withNoaction compare only: the countries to put next to the EU provision, by ISO code (["DE", "ES"]).
jurisdictionYesThe country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK, NL, IE, FI, FR, GB (UK = GB).
national_queriesNoaction compare only: for each country of compare_with, words of its statute in its language ({"DE": "ermäßigter Steuersatz"}); they sharpen the match.

Output Schema

NameRequiredDescriptionDefault
noteNoHow the call was changed, for example retried without the act.
as_ofNoThe date the wording is in force on, YYYY-MM-DD.
queryNoThe question as searched.
avisosNoThe warnings in the country's language, to pass on in the answer (Spain).
reasonNoWhy the named act was not confirmed.
sourceNoThe official source: name, address and the date of the copy.
statusNoSet when the named act was not confirmed: ACT_NOT_INDEXED or ACT_SCOPE_UNRESOLVED.
resultsNoActs, provisions or search hits, depending on the action (countries on the common contract).
sourcesNoOne entry per act cited in `articles`: act_id, name, the official citation and the source address (Poland).
articlesNoThe provisions, grouped by article, each in full with its citation (Poland).
citationNoThe citation in the country's own format.
coverageNoWhat the answer covers and what it does not.
hinweiseNoThe warnings in the country's language, to pass on in the answer (Germany).
warningsNoNotes to read before answering: what was not found, not confirmed or may be out of date.
act_matchNoSays that the act name was matched by the words of a title; check it is the act meant.
amendmentsNoWhat each pending amendment of a cited act does to the returned provisions.
attributionNoThe notice the source's licence asks for.
instructionNoWhat the answer must say or check when `status` is set.
served_actsNoActs the name was matched to instead, with act_id and name.
jurisdictionNoThe country code (countries on the common contract).
requested_actNoThe act name the call asked for, when it was not confirmed.
response_typeNoPROVISIONS when provisions are returned (Poland).
freshness_warningNoActs whose published amendments are not in the returned wording; confirm their amounts, rates and deadlines.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK, NL, IE, FI, FR."New value: +"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK, NL, IE, FI, FR, GB (UK = GB)."
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
      -  "PL",
      -  "ES",
      -  "EU",
      -  "DE",
      -  "DK",
      -  "NL",
      -  "IE",
      -  "FI",
      -  "FR"
      -]New value: +[
      +  "PL",
      +  "ES",
      +  "EU",
      +  "DE",
      +  "DK",
      +  "NL",
      +  "IE",
      +  "FI",
      +  "FR",
      +  "GB",
      +  "UK"
      +]
  2. Changed2 schema fields changed
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK, NL, IE."New value: +"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK, NL, IE, FI, FR."
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
      -  "PL",
      -  "ES",
      -  "EU",
      -  "DE",
      -  "DK",
      -  "NL",
      -  "IE"
      -]New value: +[
      +  "PL",
      +  "ES",
      +  "EU",
      +  "DE",
      +  "DK",
      +  "NL",
      +  "IE",
      +  "FI",
      +  "FR"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK, NL."New value: +"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK, NL, IE."
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
      -  "PL",
      -  "ES",
      -  "EU",
      -  "DE",
      -  "DK",
      -  "NL"
      -]New value: +[
      +  "PL",
      +  "ES",
      +  "EU",
      +  "DE",
      +  "DK",
      +  "NL",
      +  "IE"
      +]
  4. Changed2 schema fields changed
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK."New value: +"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK, NL."
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
      -  "PL",
      -  "ES",
      -  "EU",
      -  "DE",
      -  "DK"
      -]New value: +[
      +  "PL",
      +  "ES",
      +  "EU",
      +  "DE",
      +  "DK",
      +  "NL"
      +]
  5. Changed2 schema fields changed
    • changedInput schema / properties / jurisdiction / description
      Previous value: -"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE."New value: +"The country whose law or register is asked about, by its ISO code (EU: the law of the European Union itself). Live: PL, ES, EU, DE, DK."
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
      -  "PL",
      -  "ES",
      -  "EU",
      -  "DE"
      -]New value: +[
      +  "PL",
      +  "ES",
      +  "EU",
      +  "DE",
      +  "DK"
      +]
  6. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark it read-only and idempotent, and the description adds substantive behavior beyond that: warnings, status, freshness_warning and act_match fields must be read before answering, and they disclose unconfirmed acts and published amendments that change wording. It also states that a named act in `act` is answered better and that the agent must take every figure from returned text rather than its own knowledge.

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 guidance is front-loaded, starting with what the tool returns and when to call it, followed by query-writing advice and warning-reading instructions. It is dense and a few sentences chain multiple clauses, but no sentence is filler.

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?

For an 11-parameter, multi-action, open-domain legal lookup with an output schema, the description covers selection, query construction, per-country variation, warning interpretation and failure behavior. Return values are covered by the output schema, so nothing an agent needs in order to call it correctly is missing.

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?

Schema description coverage is 100%, so the baseline is 3, but the description adds strategic meaning: write the query in the country's language and in the words of the statute, cover every element of the question, and name the act when known. It does not enumerate the remaining parameters (action, compare_with, national_queries), but the schema already documents them well.

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?

The opening sentence states a specific verb, resource and scope: official legislation of a country as in force on a given date, including provisions, citation and source. It also implicitly separates itself from guidance_lookup and jurisdictions by calling out 'official legislation' and pointing to `jurisdictions` for per-country rules.

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?

Explicit when-to-use rules: call before every answer resting on a provision, call again for each follow-up question, and do not reuse earlier results for a new point. It also gives a fallback ('say the legal basis was not confirmed') when the result does not answer, which is exactly the alternative behavior an agent needs.

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.