Skip to main content
Glama

Get orderability outcome (AIO-10060)

get_orderability
Read-onlyIdempotent

The AIO-10060 orderability outcome for one listed security and one client category of its home market's chapter: the router finds the issuer's home market by the subject, as for get_record, and that market's MCP produces it — one ACM-68000 signal where the evidence reaches it, or evidence_gaps with the pages checked and no signal; every element points at its chapter or record field; signed by the node (kid allooloo-eco-2026-10) and receipted at mcp.rco-records.ai with the node as writer.

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": {
      "subject": "<subject>",
      "client_category": "<client_category>"
    },
    "name": "get_orderability"
  }
}

Input Schema

NameRequiredDescriptionDefault
subjectYesISIN (best), ticker with exchange (TSX:SHOP, SHEL.L), LEI or CMR key.
client_categoryYesOne client category exactly as the market's chapter names it (the node door's /book/aio.json, client_categories).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world, non-destructive, so the bar is lower; the description still adds real substance by disclosing the two possible outcomes (a single ACM-68000 signal versus evidence_gaps listing pages checked), the per-element provenance pointers, the signing key, and the receipt location. The only gap is that it does not say what the agent should do differently in the evidence_gaps case.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the returned resource and every clause carries information, but the whole definition is a single ~80-word run-on sentence stitched together with em-dashes and parentheticals, making it hard to parse. The literal signing key ('kid allooloo-eco-2026-10') and receipt host are unusually specific detail for a selection-time description.

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?

There is no output schema, so the description must carry the return shape, and it does: the two outcome variants, the evidence_gaps content, and per-element pointers to chapter or record field. What is missing is what the agent needs when evidence_gaps comes back and how the home-market lookup fails for a subject with no chapter.

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%, so the schema already documents both parameters, which establishes a baseline of 3. The description contributes a little beyond it: subject is used to resolve the issuer's home market through the router, and client_category is scoped to the chapter's own client_categories list, but no format, matching, or error semantics are added.

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 opening clause names the resource concretely (the AIO-10060 orderability outcome for one listed security plus one client category of its home market's chapter) and the description explicitly analogizes its routing behavior to get_record, so an agent can form a working model of what comes back. Differentiation from the closer sibling get_signal is never made, and the 'chapter'/'node door' vocabulary is domain jargon an agent must already know.

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 text says the router finds the home market 'as for get_record', which hints at the family workflow but never states when to choose this over get_signal or when to skip it (e.g. if the security has no home-market chapter). No prerequisites, exclusions, or failure conditions are given.

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.