Skip to main content
Glama

Ansvar: EU Compliance & Legal Intelligence

Get Provision

get_provision
Read-only

Look up the exact text of a specific legal provision or standards-catalog control. Three addressing forms: (1) jurisdiction + law + article — use this when someone asks 'show me Article 5 of GDPR', 'what does Section 12 of the Swedish Work Environment Act say', or 'read me the text of DORA Article 11'. A U.S. federal regulation is addressed by its CFR citation: get_provision(jurisdiction='US', law='45 CFR', article='164.410') (also '45 C.F.R.' + '§ 164.410', or law='45 CFR Part 46' + article='Part 46' for a part) reaches the one corpus that serves that CFR part. An EU act is addressed by its CELEX number: get_provision(jurisdiction='EU', law='32003L0088', article='7') resolves the act through the EU legislation discovery index to its one preferred edition; several preferred editions refuse with meta.ambiguous_candidates, and a miss names discover_eu_legislation; (2) canonical_ref — the exact ref a search row's citation.lookup hint advertises (e.g. get_provision(canonical_ref='loi-2018-07-30:art-64', jurisdiction='BE')): the gateway decomposes it and resolves the same way. Pass jurisdiction alongside canonical_ref when the ref does not embed one (relayed hints already include it). (3) law as a bare corpus/source id + article as the native control/entity id, NO jurisdiction — for non-jurisdictional standards catalogs (e.g. get_provision(law='nist-800-53', article='AC-5') for NIST SP 800-53, and the same shape for nist-csf-2, nist-800-82r3, nist-ai-rmf, nist-ssdf-800-218): a search row's citation.lookup hint for these corpora already advertises this exact shape — replay it verbatim. For a national statute you have not seen in a search row, search first and replay that row's citation.lookup; a law name resolves only where Ansvar has an alias for that name. Returns the full provision text with citation metadata. A member-state jurisdiction plus an EU framework article that has a verified national transposition returns the NATIONAL transposing provision, with meta.transposition naming the swap; pass jurisdiction='EU' for the framework text itself. Where no such mapping applies, the same field may instead carry a typed disclosure describing Ansvar's verified coverage for that pair. When a national transposition IS served, the CELEX and instrument name that response reports are themselves valid law input in that jurisdiction — replay either. When a law name matches several documents or does not resolve (near matches, reason_code=law_name_unresolved), each meta.ambiguous_candidates item is an executable get_provision retry: retry_args contains jurisdiction, law (the chassis doc_id), and the original article, or jurisdiction plus canonical_ref when the resolver supplied one; retry_kind identifies which addressing form it uses, and label carries the served document title (up to 120 characters, empty when unavailable). The text content is one JSON document. Its evidence_summary field carries the 'Sources used' markdown table (the audit receipt per returned row) or a labelled zero-result note. Result rows carry url/title/subtitle display fields alongside their citation when available. meta.render_contract carries the versioned evidence-curation contract. Search in the corpus's primary language (en), then fetch the hits in the user's language with the language argument of get_provision (a code, or a short list of codes for versions side by side). Search lookup hints may include source_id, the exact routed corpus that served the row. It is valid only with the hint's nonblank canonical_ref; law and article must remain empty. Replay the whole args object unchanged so a document present in multiple corpora cannot be substituted. Do not infer source_id from the legal document id.

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

Input Schema

NameRequiredDescriptionDefault
lawNoEither the instrument the provision belongs to — a framework id ('GDPR', 'DORA') or the corpus's own law identifier — or, for a non-jurisdictional standards catalog, the bare corpus source id ('nist-800-53', 'nist-csf-2').
articleNoArticle or section number within the instrument ('5', '5(1)(a)'), or the native control id when law is a bare standards-catalog source id ('AC-5').
languageNoEdition language of the EU legislation text. One code, or a list of up to 3 codes to receive the versions side by side, each with its own citation and `language_served`. A language the requested instrument lacks falls back to English and says so in `language_fallback`. Omit for the English default. Served editions: en, nl, de, bg.
source_idNoExact routed corpus id from a search row's citation.lookup hint. Valid only with that hint's nonblank canonical_ref; law and article must remain empty. When present, that corpus's exact hit or miss is authoritative: the gateway does not fall through to a sibling corpus. Replay the hint value; do not infer it from the legal document id.
jurisdictionNoISO-2 code of the jurisdiction that owns the provision, such as EU, SE, or BE. Required for the jurisdiction+law+article form, and alongside a canonical_ref that does not embed one. Leave empty for the bare-source-id form (law='nist-800-53').
canonical_refNoThe exact reference a search row's citation.lookup hint advertises, such as 'loi-2018-07-30:art-64'. Replay it verbatim instead of decomposing it yourself; the gateway resolves it the same way as jurisdiction+law+article.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "en",
      +        "nl",
      +        "de",
      +        "bg"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "items": {
      +        "enum": [
      +          "en",
      +          "nl",
      +          "de",
      +          "bg"
      +        ],
      +        "type": "string"
      +      },
      +      "maxItems": 3,
      +      "minItems": 1,
      +      "type": "array",
      +      "uniqueItems": true
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Edition language of the EU legislation text. One code, or a list of up to 3 codes to receive the versions side by side, each with its own citation and `language_served`. A language the requested instrument lacks falls back to English and says so in `language_fallback`. Omit for the English default. Served editions: en, nl, de, bg."
      +}
  2. Changed1 schema field changed
    • removedInput schema / properties / language
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "enum": [
      -        "en",
      -        "nl",
      -        "de",
      -        "bg"
      -      ],
      -      "type": "string"
      -    },
      -    {
      -      "items": {
      -        "enum": [
      -          "en",
      -          "nl",
      -          "de",
      -          "bg"
      -        ],
      -        "type": "string"
      -      },
      -      "maxItems": 3,
      -      "minItems": 1,
      -      "type": "array",
      -      "uniqueItems": true
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "Edition language of the EU legislation text. One code, or a list of up to 3 codes to receive the versions side by side, each with its own citation and `language_served`. A language the requested instrument lacks falls back to English and says so in `language_fallback`. Omit for the English default. Served editions: en, nl, de, bg."
      -}
  3. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "en",
      +        "nl",
      +        "de",
      +        "bg"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "items": {
      +        "enum": [
      +          "en",
      +          "nl",
      +          "de",
      +          "bg"
      +        ],
      +        "type": "string"
      +      },
      +      "maxItems": 3,
      +      "minItems": 1,
      +      "type": "array",
      +      "uniqueItems": true
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Edition language of the EU legislation text. One code, or a list of up to 3 codes to receive the versions side by side, each with its own citation and `language_served`. A language the requested instrument lacks falls back to English and says so in `language_fallback`. Omit for the English default. Served editions: en, nl, de, bg."
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / source_id
      Added value: +{
      +  "default": "",
      +  "description": "Exact routed corpus id from a search row's citation.lookup hint. Valid only with that hint's nonblank canonical_ref; law and article must remain empty. When present, that corpus's exact hit or miss is authoritative: the gateway does not fall through to a sibling corpus. Replay the hint value; do not infer it from the legal document id.",
      +  "title": "Source Id",
      +  "type": "string"
      +}
  5. Changed4 schema fields changed
    • addedInput schema / properties / article / description
      Added value: +"Article or section number within the instrument ('5', '5(1)(a)'), or the native control id when law is a bare standards-catalog source id ('AC-5')."
    • addedInput schema / properties / canonical_ref / description
      Added value: +"The exact reference a search row's citation.lookup hint advertises, such as 'loi-2018-07-30:art-64'. Replay it verbatim instead of decomposing it yourself; the gateway resolves it the same way as jurisdiction+law+article."
    • addedInput schema / properties / jurisdiction / description
      Added value: +"ISO-2 code of the jurisdiction that owns the provision, such as EU, SE, or BE. Required for the jurisdiction+law+article form, and alongside a canonical_ref that does not embed one. Leave empty for the bare-source-id form (law='nist-800-53')."
    • addedInput schema / properties / law / description
      Added value: +"Either the instrument the provision belongs to — a framework id ('GDPR', 'DORA') or the corpus's own law identifier — or, for a non-jurisdictional standards catalog, the bare corpus source id ('nist-800-53', 'nist-csf-2')."
  6. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare a safe read, but the description discloses far more: national transposition substitution with `meta.transposition`, EU-vs-member-state jurisdiction switching, `meta.ambiguous_candidates` retry semantics with `retry_args`/`retry_kind`/`label`, `reason_code=law_name_unresolved`, language fallback, and the authoritative no-fallthrough behavior of `source_id`. Nothing here contradicts the read-only annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The numbered (1)/(2)/(3) addressing forms are a good front-loaded structure, but the prose is dense and runs well past what most agents will parse, with semicolon-chained clauses. Several statements (source_id replay rules, canonical_ref replay) repeat the schema descriptions almost verbatim, so some sentences do not earn their place.

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 a six-parameter, multi-form resolver with no output schema, the description covers the return shape (full provision text plus citation metadata, `evidence_summary` sources table, `meta.render_contract`, display fields) and the error/ambiguity paths. An agent has everything needed to construct a correct call in each addressing mode.

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 coverage is 100%, so baseline is 3, but the description genuinely adds meaning: concrete argument shapes ('jurisdiction=US, law=45 CFR, article=164.410'), CELEX-as-law usage, the rule that `source_id` requires a nonblank `canonical_ref` with law/article empty, and when `jurisdiction` must accompany `canonical_ref`. Some of this duplicates schema text, which keeps it from a 5.

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 and resource — 'look up the exact text of a specific legal provision or standards-catalog control' — and immediately enumerates the three addressing forms that define its scope. It is clearly distinguishable from the `search` sibling, which it explicitly tells the agent to run first when a law name is unknown.

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 routing guidance for every case: jurisdiction+law+article for named instruments, CFR citation shape for US regulations, CELEX for EU acts, `canonical_ref` replay, and a jurisdiction-free bare-source-id form for NIST catalogs. It also names the alternative when a lookup misses ('a miss names discover_eu_legislation') and tells the agent to search before fetching for unseen national statutes.

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.