Skip to main content
Glama

list_jurisdictions

Read-onlyIdempotent

List every country and state in the authenticated subscription's Lawstronaut legal corpus (name, iso, type, documents_count) — not the global unfiltered catalog, and not legal documents or full text.

When to use: Call FIRST, before any jurisdiction-scoped legal query, so you know which iso codes are valid for this credential. When not: Skip if you already have this list from earlier in the session. Do not use this to fetch documents, markdown, source files, or portals.

Parameters: Takes none — invoke with {}. Do not pass iso, country, limit, offset, or other filters; they are not accepted and would not change the result. There is no page size or default filter. Empty data means the subscription includes no jurisdictions.

Behavior: Read-only SELECT; does not create, update, or delete records, files, or credentials. The only effect is a database read. Auth: tools/call requires OAuth 2.0 or a Bearer token (401 if missing, invalid, revoked, or no active subscription). Rate limits: none at the MCP layer; safe to retry. Not cached; each call reads current subscription and portal data.

Returns: A list of jurisdictions matching the filters, with pagination information.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYesFull subscribed list, countries then states; empty if the subscription has no jurisdictions.
messageYesResult message

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / description
      Added value: +"No arguments. Call with {}. Scope comes from the authenticated subscription, not from caller-supplied filters."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "data": {
      +      "description": "Full subscribed list, countries then states; empty if the subscription has no jurisdictions.",
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "documents_count": {
      +            "description": "Number of documents in the jurisdiction",
      +            "type": "number"
      +          },
      +          "iso": {
      +            "description": "Canonical ISO code to pass to later tools, e.g. BE",
      +            "type": "string"
      +          },
      +          "name": {
      +            "description": "Jurisdiction display name, e.g. Belgium",
      +            "type": "string"
      +          },
      +          "type": {
      +            "description": "country for national, state for sub-national",
      +            "enum": [
      +              "country",
      +              "state"
      +            ],
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "iso",
      +          "type",
      +          "documents_count"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "message": {
      +      "description": "Result message",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "message",
      +    "data"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The description is rich beyond the annotations: it discloses read-only SELECT semantics, OAuth 2.0/Bearer requirements with 401 failure conditions, absence of MCP-level rate limits, non-caching, and what empty data means. However, the closing 'Returns' line ('matches the filters, with pagination information') directly contradicts the earlier statement that no filters or pagination exist, which could mislead an agent about the tool's behavior.

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?

Labeled sections (When to use / When not / Parameters / Behavior / Auth / Rate limits / Returns) front-load the scoping statement and are easy to scan. It is slightly verbose for a zero-parameter list tool, and the boilerplate 'Returns' sentence is both redundant with the output schema and inconsistent with the body.

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?

Auth, rate limits, side effects, empty-result meaning, and scope are all covered, and an output schema exists so return shape need not be restated. The only completeness defect is the contradictory filters/pagination sentence in 'Returns', which restates return info unnecessarily and conflicts with the parameters section.

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?

There are zero parameters, so the baseline is 4; the schema itself already states 'No arguments. Call with {}.' The description goes further by enumerating the specific filters an agent might hallucinate (iso, country, limit, offset) and stating they are not accepted and would not change results, plus clarifying that scope derives from the credential.

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 description gives a specific verb and resource (list every country and state), names the returned fields (name, iso, type, documents_count), and explicitly delimits scope against the global catalog, legal documents, and full text. An agent can distinguish it from siblings such as list_documents or list_full_text without opening any 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?

It provides an explicit 'When to use' rule (call FIRST before any jurisdiction-scoped query to learn valid iso codes), an explicit 'When not' rule (skip if already obtained this session), and named exclusions (not for documents, markdown, source files, or portals). This is the full when/when-not/alternative pattern.

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.