Skip to main content
Glama

Oxford Ledge

by com.oxfordledge
OverviewDiscussionsAdmin

Bond Trade Detail (Retired)

get_bond_data
Read-only

RETIRED (2026-09-13). This was single-bond trade detail by CUSIP over FINRA's public TRACE bond page; FINRA auth-walled that host in 2026-07 and Oxford Ledge holds no licence to redistribute TRACE trade data, so no CUSIP can be priced here. It makes NO network call and returns, in under a millisecond, the same FIXED-KEY envelope it always did -- cusip, type, issuer, coupon, maturity, debtType, is144A, lastPrice, lastYield, ytm, high, low, volume, tradeDate, source, fetchedAt, ytw, callable, duration, modifiedDuration, moodysRating, spRating, fitchRating, error -- with every price field null, plus {status: 'retired', unavailable: true, note, use_instead: 'ol_bond_directory_screen'}; error carries the retirement note, or 'CUSIP must be at least 6 characters' when the input itself is malformed, so a caller can tell their input from our outage. The name is kept because the wheel and the licence-class registries pin it. Use ol_bond_directory_screen (the persisted LQD/HYG corporate-bond directory: issuer, grade, coupon and maturity -- reference data, no prices) or get_debt_maturities for one issuer's own maturity schedule. Source: none (retired FINRA TRACE endpoint). Needs an Oxford Ledge API key that the client's operator configures; anonymous callers are refused.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cusipYes9-character CUSIP identifier (e.g. 037833AK6 for Apple)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond readOnlyHint=true: no network call, sub-millisecond fixed envelope, every price field null, a status/unavailable/note/use_instead block, and an error channel that distinguishes malformed input ('CUSIP must be at least 6 characters') from an outage. It also discloses the API-key auth requirement and that anonymous callers are refused.

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?

Front-loaded with 'RETIRED (2026-09-13)' and front-loads the replacement tool. It is dense and long, and the 22-key envelope enumeration is borderline padding, but each clause carries retirement, licensing, return-shape, or error information.

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?

With no output schema, the description carries the full burden and does so: it enumerates the returned envelope, explains the status fields, the error semantics, and the auth requirement. Nothing needed to call it correctly is missing.

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 single cusip parameter is already documented as a 9-character CUSIP. The description adds only the malformed-input error threshold (6 characters), which is a behavioral detail rather than added parameter semantics, so baseline 3 is appropriate.

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 states precisely what the tool is (retired FINRA TRACE single-bond lookup by CUSIP), what it now does (fixed-key envelope, no network call), and how it differs from siblings by naming ol_bond_directory_screen and get_debt_maturities. An agent can tell instantly it is a retired stub, not a live price source.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing: 'Use ol_bond_directory_screen ... or get_debt_maturities for one issuer's own maturity schedule.' It also states why this tool cannot be used (TRACE host auth-walled, no redistribution licence), leaving no ambiguity about when to call it.

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

All Oxford Ledge toolsInspect
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