Skip to main content
Glama

Resolve issuer

resolve_issuer
Read-onlyIdempotent

Find a listed company by ticker, ISIN or LEI. The router names the issuer's home market and forwards to that market's MCP for the record summary.

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": {
      "identifier": "<identifier>"
    },
    "name": "resolve_issuer"
  }
}

Input Schema

NameRequiredDescriptionDefault
identifierYesTicker with or without exchange (SHOP, TSX:SHOP, SHEL.L, BHP.AX, D05.SI, NESN.SW, SAP.DE, 7203.T, 005930.KS), ISIN, LEI, an exact legal name or a sourced alias.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), and the description usefully adds the routing behavior — the lookup is delegated to the issuer's home market MCP. It says nothing about failure behavior for unknown or ambiguous identifiers, which is the main behavioral risk for a resolver.

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?

Two short sentences, front-loaded with the lookup purpose followed by the routing note. No wasted wording, though the second sentence's value depends on the reader already knowing what 'the record summary' is.

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 full schema coverage and rich annotations, this is close to sufficient: it names the result ('record summary') and the routing model. Minor gap is the absence of any note on precedence when an identifier is ambiguous or the market cannot be determined.

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% and the parameter's own description already enumerates ticker formats, ISIN, LEI, legal name and alias. The description's identifier list largely restates that, adding no new syntax or disambiguation rules beyond the schema.

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?

States a specific verb and resource ('Find a listed company') plus the accepted identifier kinds, and adds that the router forwards to the issuer's home-market MCP. It does not explicitly differentiate itself from the sibling get_ticker, so it falls short of a 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?

The description implies when to use it (when you have a ticker, ISIN, LEI or legal name and want to resolve the entity), but gives no explicit when-not guidance or comparison to get_ticker or list_nodes. Usage is inferable rather than stated.

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.