Skip to main content
Glama

VeriActa: countries and what each offers

jurisdictions
Read-onlyIdempotent

Lists the countries VeriActa serves and what each offers: law, classifications, official guidance, company registers. With a jurisdiction, returns that country's notes on how to ask each tool: the language and terms to search in, how acts are named and cited, which classification systems and registers exist. Call it once when you first work with a country, or when a tool answers NOT_AVAILABLE. Free: it spends no credits.

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

Input Schema

NameRequiredDescriptionDefault
jurisdictionNoA country code, to get that country's notes on how to ask each tool. Leave out to list every live country.

Output Schema

NameRequiredDescriptionDefault
nextNoWhat to call for a country's notes.
coverageNoThe coverage matrix: per capability and function, which live country has it.
jurisdictionsNoThe live countries: code, name, languages and what each offers (law, classification, guidance, company); with a country asked for, its notes on how to ask each tool.
notes_languageNoWhich language the notes are in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / jurisdiction / enum
      Previous value: -[
      -  "PL",
      -  "ES",
      -  "EU",
      -  "DE"
      -]New value: +[
      +  "PL",
      +  "ES",
      +  "EU",
      +  "DE",
      +  "DK"
      +]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds context beyond that: it is free ('spends no credits') and it is meant as a one-time orientation step, which matters for cost-sensitive or error-recovery decision making.

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 sentences, front-loaded with the list mode and then the filtered mode, followed by the usage trigger and cost note. The long semicolon-delimited list in the second sentence is dense but each clause carries distinct information.

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?

An output schema exists, so return values need not be described in prose. The description still covers the two modes, the meaning of the parameter, when to call, and the cost profile, which is complete for a one-parameter orientation tool.

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% and the enum is fully documented, so the baseline is 3. The description adds meaningful detail about what the jurisdiction value returns: language and terms to search, act naming/citation conventions, and which classification systems and registers exist.

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 ('Lists the countries VeriActa serves and what each offers') and then specifies the second mode with a jurisdiction parameter ('returns that country's notes on how to ask each tool'). An agent can distinguish this from law_lookup/company_lookup without opening the schema.

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 explicit triggers: 'Call it once when you first work with a country, or when a tool answers NOT_AVAILABLE.' These are concrete when-to-use conditions, including an error-recovery case, and no alternative tool is proposed instead because this is the entry point.

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.