openregistry

Per-country schema reference and tool-support matrix

list_jurisdictions

Read-onlyIdempotent

Retrieve per-country reference data dictionary for jurisdictions. Pass a country code to get full schema including registry info, company ID format, status mappings, and supported tools. Pass a tool name to see which jurisdictions implement it.

Instructions

Per-country reference data dictionary. Two modes — pass EXACTLY ONE of: • jurisdiction: 'GB' — full schema for one country: registry name + URL, data license, company ID format with examples, native status values + mapping to the unified active/inactive/dissolved/unknown enum, list of supported tools, list of field names available in jurisdiction_data sub-objects (profile/filing/officer/shareholder/psc/charge), free-text quirks notes, and the global_search_excluded flag. • supports_tool: 'get_officers' — cross-country matrix for one tool: which jurisdictions implement it (with their registry names) and which don't. Calling with no parameters returns a structured 400 with both shapes documented. For server-level info (codes list, version, rate limits) call about instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`jurisdiction`	No	ISO 3166-1 alpha-2 country code (case-insensitive; CA subdivisions hyphenated like 'CA-BC'). Returns the full per-country schema. Mutually exclusive with `supports_tool`.
`supports_tool`	No	Tool name (e.g. 'get_officers', 'get_persons_with_significant_control'). Returns the matrix of which jurisdictions implement this tool. Mutually exclusive with `jurisdiction`.

Output Schema

TableJSON Schema

Name	Required	Description
`queried_at`	Yes	ISO-8601 + Europe/London timezone stamp for when the registry was queried.
`jurisdiction`	No	Populated in single-country mode: carries the JurisdictionMetadata for the requested country.
`tool`	No	Populated in cross-country support-matrix mode: echoes the tool name that was queried.
`supported_count`	No
`supported_in`	No
`not_supported_count`	No
`not_supported_in`	No
`hint`	No

Tool Definition Quality

A4.9/5.0

Behavior5/5

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

Annotations (readOnlyHint, destructiveHint, idempotentHint) already indicate safe, idempotent read behavior. The description adds rich behavioral context: when no parameters are passed, it returns a structured 400 with both shapes documented. This goes beyond annotations without contradiction.

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?

The description is in two sentences, each serving a distinct purpose: first describes the two modes, second mentions the no-parameter return and directs to about for server info. No wasted words, excellent structure.

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?

Given the output schema is provided, the description doesn't need to repeat return types. It covers all necessary aspects: modes, no-param behavior, and cross-reference to sibling tool. Highly complete.

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?

The schema already covers both parameters with 100% coverage. The description adds value by describing the output shapes for each mode in detail, and notes case-insensitivity and hyphenation for subdivisions, which is not in the schema.

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 clearly states the tool provides 'per-country reference data dictionary' and explicitly describes two mutually exclusive modes (jurisdiction and supports_tool), with detailed outputs for each. It distinguishes itself from sibling tools like about by stating where to get server-level info.

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?

The description explicitly says 'pass EXACTLY ONE of' and describes the two modes, including what happens with no parameters (returns 400). It names the sibling tool about for server-level info, providing clear when-to-use guidance.

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

Install Server

Latest Blog Posts

Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
open source
OpenAI
Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sophymarine/openregistry'

If you have feedback or need assistance with the MCP directory API, please join our Discord server