Skip to main content
Glama

Sisoco One LEI

Get an LEI record

sisoco_get_lei_record
Read-onlyIdempotent

Returns the GLEIF record for a Legal Entity Identifier: legal name, registered and headquarters addresses, legal form, registration authority and number, entity and registration status (e.g. LAPSED). For its parent companies call sisoco_get_lei_parents. Source: GLEIF (CC0). Cost: 1 lookup (same as GET /v1/entities/lei/{lei}).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lei": "<lei>"
    },
    "name": "sisoco_get_lei_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
leiYesLegal Entity Identifier (20 characters), e.g. 2138002P5RNKC5W2JZ46

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the description's added value is the data provenance (GLEIF, CC0), the billing/cost model ('1 lookup, same as GET /v1/entities/lei/{lei}'), and a sample status value (LAPSED). That is real context beyond structured fields, though it says nothing about behavior on an unknown or malformed LEI.

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?

Three sentences, each doing distinct work: what is returned, which sibling to use otherwise, and provenance/cost. The payload description is front-loaded and nothing is redundant.

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?

For a single-parameter lookup with an output schema already defining the return shape, the definition is nearly complete — it supplies source, cost, and payload scope. The only gap is error/failure behavior for invalid or unregistered LEIs, which an agent calling this would occasionally need.

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 description coverage is 100% and the single required parameter is fully documented there (20 characters, with an example). The description adds no further meaning about the identifier's format or validation, so the schema carries this dimension entirely.

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?

Specific verb (returns) + resource (GLEIF record for an LEI) plus an enumeration of the payload fields (legal name, addresses, legal form, registration authority/number, entity status). It also explicitly distinguishes itself from the sibling that handles related entities: 'For its parent companies call sisoco_get_lei_parents.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives one explicit routing rule to a sibling (use sisoco_get_lei_parents for parent companies) and identifies the lookup by its underlying endpoint, which is clear context for when to reach for it. It does not address when to prefer sisoco_search_company or sisoco_check_company instead, so the guidance is clear but not exhaustive.

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.