Skip to main content
Glama

VeriActa: official guides and rulings

guidance_lookup
Read-onlyIdempotent

Official guidance of a country's authorities: handbooks, brochures and rulings that explain how to fill in a form or apply a rule. Search first, then read the document and page a result names. Cite the document and page. Guidance explains the law and is not the law: confirm the legal basis with law_lookup.

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

Input Schema

NameRequiredDescriptionDefault
pageNoThe page of `document` to read.
limitNoPassages a search returns (1 to 10, default 5).
queryNoThe issue or the name of a form field, in the words of the document. Required unless you give `document` and `page`.
issuerNoWhose documents to search, where the country has several (Poland: ZUS, MF, KE).
sourceNoA named collection, where the country has more than one (Poland: "eureka" for individual tax rulings; default the guides).
documentNoA document id from an earlier result, to read it.
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).

Output Schema

NameRequiredDescriptionDefault
modeNoA search, one page of a document, or a page read by its address.
noteNoWhere the text of a page read starts, or what is left of a document read by address.
sourceNoWhich authorities' documents are searched; they explain the law and are not the law.
outlineNoThe headings of the document read by address, with their pages.
passagesNoThe passages: document, issuer, page, heading, text and the address of the source.
warningsNoNotes to read before answering: what was not found, not confirmed or may be out of date.
pages_totalNoPages or parts of the document read by address.

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.4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond them: the search-then-read two-mode operation, the expectation that document ids and page numbers come from prior results, and the citation duty. It stops short of noting coverage limits or anything about result freshness, which keeps it from a 5.

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?

Four short sentences, front-loaded with what the resource is, then the workflow, then the caveat. Each sentence carries a distinct instruction (identify, search-then-read, cite, defer to law_lookup) with no restatement or filler.

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 an output schema present, return values need no explanation, and the description covers purpose, workflow, citation and the sibling boundary for a seven-parameter lookup tool. The only optional gap is any note on jurisdiction coverage or the Polish source/issuer collections, which the schema already handles.

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 issuer/source examples and the query-vs-document/page dependency, so the schema carries the parameter burden. The description's 'page a result names' lightly reinforces that document and page are follow-up inputs, but adds no syntax or format detail the schema lacks, and never mentions issuer, source, limit or jurisdiction.

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 resource ('official guidance ... handbooks, brochures and rulings') and what it is for ('explain how to fill in a form or apply a rule'), which an agent can immediately separate from law_lookup, classification_lookup or company_lookup. The final sentence sharpens the boundary by declaring guidance is explanatory, not the law itself.

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?

Gives an explicit two-step workflow ('Search first, then read the document and page a result names'), a citation obligation, and a named alternative with its selecting condition ('confirm the legal basis with law_lookup'). This is as close to when/when-not/alternatives as a description gets for a read-only lookup tool.

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.