Skip to main content
Glama
Sign In

LawDB

by eu.lawdb
OverviewDiscussionsAdmin

List Jurisdictions Tool

list_jurisdictions
Read-onlyIdempotent

Lists the jurisdictions, content languages and courts this database covers.

Call this once before using filters: it returns the exact jurisdiction codes and court slugs that search_legal_documents accepts. Current coverage includes Germany (de), the European Union (eu), the Council of Europe / European Court of Human Rights (coe), the United Nations / International Court of Justice (un), and international law / Permanent Court of Arbitration (int). An invented court slug matches nothing, so do not guess one.

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
languageNoLanguage for court and jurisdiction names. Defaults to German.de

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds real behavior beyond that: it is a prerequisite/discovery call, its results are the authoritative code vocabulary, and guessing values silently yields zero matches. It stops short of describing the response shape in detail, but names the two key returned fields.

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?

Front-loaded with the action and the imperative call-once instruction, then supporting coverage detail, with zero filler sentences. The enumerated coverage list is slightly verbose for data the tool itself returns, but it usefully signals scope before the first call.

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 one-parameter discovery tool with no output schema, the description supplies the missing return-value context (jurisdiction codes and court slugs), the calling sequence, and the failure mode for bad inputs. Nothing an agent needs in order to call it correctly is absent.

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 coverage is 100% with a single enum-backed `language` parameter fully documented in the schema, so baseline 3 applies. The description's mention of 'content languages' refers to returned data rather than the input parameter and could momentarily be confused with it, adding no real parameter meaning.

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?

Names a specific verb and resource ('Lists the jurisdictions, content languages and courts this database covers') and immediately ties the output to the `jurisdiction` and `court` fields that `search_legal_documents` consumes, which separates it cleanly from the sibling search/get tools.

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?

States an explicit sequencing rule ('Call this once before using filters') plus a negative constraint ('An invented court slug matches nothing, so do not guess one'). That is both a when-to-use and a when-not-to-improvise instruction, with the downstream alternative tool named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All LawDB toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources