Skip to main content
Glama

Get the issuer record

get_record
Read-onlyIdempotent

Return the full issuer record, served by the MCP of the issuer's home market. The router stores no records.

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": "get_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNo
identifierYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the record is served by the MCP of the issuer's home market, and the router itself stores nothing, which tells the agent the result is federated through a remote source rather than read from a local cache. It does not discuss failure modes when the home-market MCP is unavailable.

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?

Two short sentences with zero filler, the core action stated first and the routing caveat second. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The routing/serving note usefully explains where data comes from, but with no output schema the description never sketches what the 'full issuer record' contains, and the unexplained 'version' parameter leaves a real hole for a two-argument read tool. Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across both parameters, so the description must compensate and largely does not. It implies 'identifier' identifies the issuer, but gives no format or provenance (ISIN, internal ID, alias?), and the 'version' parameter is never explained at all despite being the one non-obvious argument.

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?

The description pairs a specific verb ('Return') with a specific resource ('the full issuer record'), so the agent knows this is a record fetch rather than a resolution or listing call. It stops short of naming or contrasting the closest sibling (resolve_issuer), leaving the agent to infer the boundary from the word 'full'.

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 only implied: the phrase 'full issuer record' plus the required identifier suggest this is the call to make once an issuer is already identified. There is no explicit when-to-use or when-not guidance, and no statement of prerequisites for obtaining a valid identifier first.

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.