resolve_issuerFind a listed company by ticker, ISIN or LEI: the apex names the owning node and forwards to that node's regional door for the record summary.
| Name | Required | Description | Default |
|---|---|---|---|
| identifier | Yes | Ticker 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. |
Changes observed during successful MCP inspections.
Input schema / properties / identifier / descriptionPrevious value: -"Ticker (SHOP, TSX:SHOP, SHOP.TO, SHEL, LSE:SHEL, SHEL.L, AIM:4BB, AQSE:DGQ, BHP, ASX:BHP, BHP.AX, D05, D05.SI, NESN.SW, SAP.DE; on the Euronext nodes the ISIN is the key: XPAR:FR0000120271, AMS:NL0000009165; 7203.T, 005930.KS), ISIN (CA82509L1076, GB00BP6MXD84, AU000000BHP4, SG1L01001701, CH0038863350, DE0007164600, FR0000120271, NL0000009165), LEI (20 characters), or an exact legal name or sourced alias."New value: +"Ticker 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."Input schema / properties / identifier / descriptionPrevious value: -"Ticker (SHOP, TSX:SHOP, SHOP.TO, SHEL, LSE:SHEL, SHEL.L, AIM:4BB, AQSE:DGQ, BHP, ASX:BHP, BHP.AX, D05, D05.SI, NESN.SW, SAP.DE; on the Euronext nodes the ISIN is the key: XPAR:FR0000120271, AMS:NL0000009165), ISIN (CA82509L1076, GB00BP6MXD84, AU000000BHP4, SG1L01001701, CH0038863350, DE0007164600, FR0000120271, NL0000009165), LEI (20 characters), or an exact legal name or sourced alias."New value: +"Ticker (SHOP, TSX:SHOP, SHOP.TO, SHEL, LSE:SHEL, SHEL.L, AIM:4BB, AQSE:DGQ, BHP, ASX:BHP, BHP.AX, D05, D05.SI, NESN.SW, SAP.DE; on the Euronext nodes the ISIN is the key: XPAR:FR0000120271, AMS:NL0000009165; 7203.T, 005930.KS), ISIN (CA82509L1076, GB00BP6MXD84, AU000000BHP4, SG1L01001701, CH0038863350, DE0007164600, FR0000120271, NL0000009165), LEI (20 characters), or an exact legal name or sourced alias."Input schema / properties / identifier / descriptionPrevious value: -"Ticker (SHOP, TSX:SHOP, SHOP.TO, SHEL, LSE:SHEL, SHEL.L, AIM:4BB, AQSE:DGQ, BHP, ASX:BHP, BHP.AX, D05, D05.SI, NESN.SW, SAP.DE), ISIN (CA82509L1076, GB00BP6MXD84, AU000000BHP4, SG1L01001701, CH0038863350, DE0007164600), LEI (20 characters), or an exact legal name or sourced alias."New value: +"Ticker (SHOP, TSX:SHOP, SHOP.TO, SHEL, LSE:SHEL, SHEL.L, AIM:4BB, AQSE:DGQ, BHP, ASX:BHP, BHP.AX, D05, D05.SI, NESN.SW, SAP.DE; on the Euronext nodes the ISIN is the key: XPAR:FR0000120271, AMS:NL0000009165), ISIN (CA82509L1076, GB00BP6MXD84, AU000000BHP4, SG1L01001701, CH0038863350, DE0007164600, FR0000120271, NL0000009165), LEI (20 characters), or an exact legal name or sourced alias."Input schema / properties / identifier / descriptionPrevious value: -"Ticker (SHOP, TSX:SHOP, SHOP.TO, SHEL, LSE:SHEL, SHEL.L, AIM:4BB, AQSE:DGQ, BHP, ASX:BHP, BHP.AX, D05, D05.SI), ISIN (CA82509L1076, GB00BP6MXD84, AU000000BHP4, SG1L01001701), LEI (20 characters), or an exact legal name or sourced alias."New value: +"Ticker (SHOP, TSX:SHOP, SHOP.TO, SHEL, LSE:SHEL, SHEL.L, AIM:4BB, AQSE:DGQ, BHP, ASX:BHP, BHP.AX, D05, D05.SI, NESN.SW, SAP.DE), ISIN (CA82509L1076, GB00BP6MXD84, AU000000BHP4, SG1L01001701, CH0038863350, DE0007164600), LEI (20 characters), or an exact legal name or sourced alias."Input schema / properties / identifier / descriptionPrevious value: -"Ticker (SHOP, TSX:SHOP, SHOP.TO, SHEL, LSE:SHEL, SHEL.L, AIM:4BB, AQSE:DGQ, BHP, ASX:BHP, BHP.AX), ISIN (CA82509L1076, GB00BP6MXD84, AU000000BHP4), LEI (20 characters), or an exact legal name or sourced alias."New value: +"Ticker (SHOP, TSX:SHOP, SHOP.TO, SHEL, LSE:SHEL, SHEL.L, AIM:4BB, AQSE:DGQ, BHP, ASX:BHP, BHP.AX, D05, D05.SI), ISIN (CA82509L1076, GB00BP6MXD84, AU000000BHP4, SG1L01001701), LEI (20 characters), or an exact legal name or sourced alias."Input schema / properties / identifier / descriptionPrevious value: -"Ticker (SHOP, TSX:SHOP, SHOP.TO, SHEL, LSE:SHEL, SHEL.L, AIM:4BB, AQSE:DGQ), ISIN (CA82509L1076, GB00BP6MXD84), LEI (20 characters), or an exact legal name or sourced alias."New value: +"Ticker (SHOP, TSX:SHOP, SHOP.TO, SHEL, LSE:SHEL, SHEL.L, AIM:4BB, AQSE:DGQ, BHP, ASX:BHP, BHP.AX), ISIN (CA82509L1076, GB00BP6MXD84, AU000000BHP4), LEI (20 characters), or an exact legal name or sourced alias."Input schema / properties / identifier / descriptionPrevious value: -"Ticker (SHOP, TSX:SHOP, SHOP.TO), ISIN (CA82509L1076), LEI (20 characters), or an exact legal name or sourced alias (CPKC)."New value: +"Ticker (SHOP, TSX:SHOP, SHOP.TO, SHEL, LSE:SHEL, SHEL.L, AIM:4BB, AQSE:DGQ), ISIN (CA82509L1076, GB00BP6MXD84), LEI (20 characters), or an exact legal name or sourced alias."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior. The description adds genuinely new behavioral context — that the apex node resolves ownership and forwards to a regional node for the summary — but says nothing about failure modes (unknown identifier), latency, or what the summary contains.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence, front-loaded with the purpose before the routing detail, with no filler. The trailing architecture jargon ('apex names the owning node and forwards to that node's regional door') is dense and slightly obscures rather than clarifies.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations covering the return value, the description carries the burden of explaining results, yet only says 'the record summary' without defining it. For a single-parameter lookup the input side is well covered, but the output side and the internal routing metaphor remain under-specified.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the parameter description already spells out ticker formats, ISIN, LEI, exact legal name and sourced alias. The description adds little beyond repeating 'ticker, ISIN or LEI', and in fact omits the legal-name and alias forms the schema supports, so it is baseline at best.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a concrete verb ('Find') and resource ('listed company') and enumerates the identifier kinds (ticker, ISIN, LEI), so an agent can tell what the tool does. However, it never contrasts itself with the nearby sibling get_record, even though it also mentions returning 'the record summary', leaving some ambiguity about which tool to pick.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for looking up a company from an identifier, but offers no explicit when-to-use guidance, no when-not-to-use, and no comparison to siblings like get_record or list_nodes. The agent must infer that resolution is the entry point to the record summary.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.