Issuerwire — capital markets news for AI agents

Resolve Issuer

resolve_issuer

Who is this issuer? A name, ticker, ISIN, LEI, CIK or Companies House number (optionally a market: US · UK · CA · DE · FR · NL · CH · AU · SG · JP · KR · HK) resolves to the issuer keys on the record, with name, tickers, status and claim standing. Open.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`market`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Since no annotations are provided, the description bears the full burden. It successfully discloses the expected outputs, specifically listing 'name, tickers, status and claim standing,' which is valuable behavioral context.

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 single paragraph is highly dense and effective, front-loading the core functionality and key constraints without unnecessary filler. It manages high informational entropy efficiently.

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?

Given the complexity of the inputs (multiple identifier types, market scoping), the description is extremely complete. It explains the 'what,' 'how,' and 'where' of the resolution process.

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

Parameters5/5

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

With 0% schema description coverage, the description is critical. It explicitly details what the 'query' parameter accepts (Name, Ticker, ISIN, LEI, CIK, Companies House number) and defines the scope of the 'market' parameter.

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?

The description clearly defines the goal: identifying an issuer given various identifiers. It uses strong verbs ('resolves') and specifies the target entities ('issuer keys on the record').

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?

The definition provides excellent guidance on the *conditions* for use by listing all acceptable input identifiers and constraints (market). It does not explicitly compare itself to sibling tools, but its scope is well-defined.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Issuerwire — capital markets news for AI agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?