Skip to main content
Glama

Sisoco One

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). 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

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower; the description still adds real context: data provenance and licensing (GLEIF, CC0), the cost model, and that status fields can hold values like LAPSED. It does not state what happens when the LEI is unknown or malformed.

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?

A single dense sentence with the resource and returned fields front-loaded, plus a compact provenance/cost tag at the end. No filler; the field enumeration is long but functional.

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 a full output schema, the description covers what is fetched, where it comes from, and what it costs. Missing only edge-case behavior (not-found or invalid LEI handling), which is minor at this complexity.

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?

Only one parameter and schema description coverage is 100% (format, 20-character length, and a worked example are all in the schema). The description repeats 'Legal Entity Identifier' without adding format or validation meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource: 'Returns the GLEIF record for a Legal Entity Identifier', followed by an enumeration of the fields returned (legal name, addresses, legal form, registration authority/number, statuses). An agent can tell this is a single-entity LEI lookup, distinct from a company search or ownership-chain tool. It stops short of naming a sibling, so 4 rather than 5.

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

Usage Guidelines3/5

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

Usage is implied by the required 'lei' argument and the 'Cost: 1 lookup' note, which hints this is the cheap direct-fetch path. There is no explicit when-to-use/when-not guidance or comparison to sisoco_search_company or sisoco_check_company for agents that only have a name.

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.

Resources