Skip to main content
Glama

Decode Registration Authority

decode_registration_authority
Read-onlyIdempotent

Decode a GLEIF Registration Authority (RA) code to the national business register's name, website and jurisdiction(s). This is the code GLEIF publishes as registration_authority on every LEI record (get_lei, search_lei results), naming the register that assigned the entity's registered_as id, "RA000585" decodes to the UK's Companies House, for example. Bare digits are zero-padded and prefixed with "RA" automatically ("585" -> "RA000585"). get_lei already decodes this field inline as registration_authority_decoded, call this tool directly only when you have a bare code from elsewhere.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "RA000585"
    },
    "name": "decode_registration_authority"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesGLEIF Registration Authority code, "RA" + 6 digits, e.g. "RA000585" (UK Companies House). Bare digits (e.g. "585") are accepted and normalized.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description still adds real behavior beyond that: it normalizes input ('Bare digits are zero-padded and prefixed with "RA" automatically'), and it explains the field's provenance on LEI records. It does not discuss error handling for unknown codes, which keeps it below 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose and the example come first, then normalization, then the routing advice, which is a sensible front-loaded order. It is denser than strictly necessary (the `registered_as`/`registration_authority` linkage is a long clause), but no sentence is filler.

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 single-parameter lookup with no output schema, the description says what the input looks like, what it returns, and when to prefer a sibling. Nothing an agent needs in order to call it correctly is missing.

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 already 100% and the parameter description repeats the normalization note, so the structured data does most of the work. The description does add interpretive meaning: it explains what the code identifies (the register that assigned the entity's `registered_as` id) and gives a concrete decode example, going slightly beyond 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?

States a specific verb ('Decode'), a specific resource ('GLEIF Registration Authority (RA) code'), and names exactly what comes back: the national business register's name, website and jurisdictions. The concrete example ('RA000585' -> UK Companies House) removes any ambiguity about what this tool operates on.

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?

Explicitly tells the agent when NOT to use it: 'get_lei already decodes this field inline as registration_authority_decoded, call this tool directly only when you have a bare code from elsewhere.' That is an unambiguous alternative-and-condition statement, which is exactly what the guidance dimension asks for.

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.