Equibles

Debt Instrument Detail

GetDebtInstrument

Read-only

Get one durable debt instrument by its Equibles identifier. Returns current balances, linked filing observation, verified covenant bullets, exact source quotes, and governing or amending SEC documents. History, covenants, and documents are independently paged. Use GetDebtProfile first to obtain the instrument identifier.

Input Schema

Name	Required	Description
`ticker`	Yes	Stock ticker symbol (e.g., AAPL, MSFT), or MIC:TICKER (e.g., XPAR:AIR) for a listing outside the US.
`maxHistory`	No	Maximum filing-history rows to return (default 10, max 10).
`instrumentId`	Yes	Debt instrument identifier returned by GetDebtProfile.
`maxCovenants`	No	Maximum covenant rows to return (default 10, max 10).
`maxDocuments`	No	Maximum governing/update documents to return (default 10, max 10).
`historyOffset`	No	Zero-based filing-history offset for paging.
`covenantOffset`	No	Zero-based covenant offset for paging.
`documentOffset`	No	Zero-based document offset for paging.
`evidenceOffset`	No	Zero-based character offset into the exact evidence for these history and covenant pages.
`maxEvidenceCharacters`	No	Maximum exact-evidence characters to return for these history and covenant pages (default 0, max 12000). Use a positive value to read evidence losslessly in character pages.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / ticker / description

Previous value: -"Stock ticker symbol (e.g., AAPL, MSFT)."New value: +"Stock ticker symbol (e.g., AAPL, MSFT), or MIC:TICKER (e.g., XPAR:AIR) for a listing outside the US."

Changed8 schema fields changedSep 4, 2026

addedInput schema / properties / covenantOffset

Added value: +{
+  "default": 0,
+  "description": "Zero-based covenant offset for paging.",
+  "type": "integer"
+}

addedInput schema / properties / documentOffset

Added value: +{
+  "default": 0,
+  "description": "Zero-based document offset for paging.",
+  "type": "integer"
+}

addedInput schema / properties / evidenceOffset

Added value: +{
+  "default": 0,
+  "description": "Zero-based character offset into the exact evidence for these history and covenant pages.",
+  "type": "integer"
+}

addedInput schema / properties / historyOffset

Added value: +{
+  "default": 0,
+  "description": "Zero-based filing-history offset for paging.",
+  "type": "integer"
+}

addedInput schema / properties / maxCovenants

Added value: +{
+  "default": 10,
+  "description": "Maximum covenant rows to return (default 10, max 10).",
+  "type": "integer"
+}

addedInput schema / properties / maxDocuments

Added value: +{
+  "default": 10,
+  "description": "Maximum governing/update documents to return (default 10, max 10).",
+  "type": "integer"
+}

addedInput schema / properties / maxEvidenceCharacters

Added value: +{
+  "default": 0,
+  "description": "Maximum exact-evidence characters to return for these history and covenant pages (default 0, max 12000). Use a positive value to read evidence losslessly in character pages.",
+  "type": "integer"
+}

addedInput schema / properties / maxHistory

Added value: +{
+  "default": 10,
+  "description": "Maximum filing-history rows to return (default 10, max 10).",
+  "type": "integer"
+}

AddedSep 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses the shape of the payload (balances, covenant bullets, exact quotes, SEC documents) and that history, covenants, and documents page independently, which tells the agent the response is multi-section and paginated.

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?

Three sentences, no filler. The identity/return summary is front-loaded, the paging caveat follows, and the prerequisite is stated last as an actionable next step. Every sentence carries distinct 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?

For a 10-parameter read tool with no output schema, the description supplies the missing pieces: what the response contains, that it is three independently paged sections, and how to obtain the required identifier. There is no output schema, so enumerating return content is the correct use of the description.

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

Parameters4/5

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

Schema description coverage is 100%, so a baseline of 3 would be warranted on its own. The description earns above baseline by clarifying that the three collections are paged independently, which explains why there are separate offset/max pairs for history, covenants, and documents rather than a single paging control.

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?

States a specific verb and resource ('Get one durable debt instrument by its Equibles identifier') and enumerates the returned content. It clearly distinguishes itself from the sibling GetDebtProfile by positioning that tool as the identifier source rather than a substitute.

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?

Explicitly names the prerequisite flow ('Use GetDebtProfile first to obtain the instrument identifier' and that the id is 'returned by GetDebtProfile'), which is exactly the routing an agent needs. It stops short of stating when-not to use it or what to do if the identifier is unknown, so it is strong but not exhaustive.

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

All Equibles tools Inspect

Try in Browser