Skip to main content
Glama

equibles

by io.github.daniel3303

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

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesStock ticker symbol (e.g., AAPL, MSFT).
maxHistoryNoMaximum filing-history rows to return (default 10, max 10).
instrumentIdYesDebt instrument identifier returned by GetDebtProfile.
maxCovenantsNoMaximum covenant rows to return (default 10, max 10).
maxDocumentsNoMaximum governing/update documents to return (default 10, max 10).
historyOffsetNoZero-based filing-history offset for paging.
covenantOffsetNoZero-based covenant offset for paging.
documentOffsetNoZero-based document offset for paging.
evidenceOffsetNoZero-based character offset into the exact evidence for these history and covenant pages.
maxEvidenceCharactersNoMaximum 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. Dates show when Glama detected each change.

  1. Changed8 schema fields changed
    • 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"
+}
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already convey readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral context by revealing that the response bundles current balances, a filing observation, covenant bullets, exact source quotes, and SEC documents, and that history, covenants, and documents are independently paged. This goes beyond the annotation baseline.

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 with no filler: the first states the core purpose, the second summarizes the returned data, and the third covers paging and prerequisite. The most important information is front-loaded.

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?

For a 10-parameter read tool with no output schema, the description adequately describes what will be returned, notes that subresources are paged independently, and routes the agent to the prerequisite call. Remaining details like evidence character limits are fully specified in the schema.

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 description coverage is 100%, with all ten parameters documented including defaults, maximums, and offsets. The description reinforces that instrumentId comes from GetDebtProfile and that collections page independently, but it does not materially add meaning beyond what the schema already states.

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 a specific verb ('Get'), a specific resource ('one durable debt instrument'), and a key ('Equibles identifier'), then enumerates the exact return contents. It clearly distinguishes this from the sibling GetDebtProfile by positioning that tool as the source of the identifier.

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 description explicitly says 'Use GetDebtProfile first to obtain the instrument identifier', giving the agent a concrete prerequisite and call sequence. It does not mention when not to use the tool or list alternative detail tools, but GetDebtProfile is the relevant sibling and the guidance is clear enough.

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

All equibles toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, with detailed descriptions that cross-reference related alternatives. A few near-duplicate names could cause misselection, notably SearchDocument versus SearchDocuments and GetCftcPositioning versus GetLatestCftcPositioning.

Naming Consistency5/5

Tool names consistently follow a VerbNoun camelCase pattern: Get for retrievals, Search for discovery, List/Read for document access, and Add/Close/Remove/Update/Watch/Create/Delete for portfolio mutations. Despite the large count, there is no mixing of naming conventions or unpredictable verb styles.

Tool Count1/5

108 tools is an extreme surface area, far beyond the 3-15 well-scoped range and well past the 25+ threshold. Even for a broad financial data platform, this creates a heavy selection burden and substantial context overhead for agents.

Completeness4/5

The server covers an unusually wide domain: prices, fundamentals, SEC filings, options, insider activity, 13F holdings, short interest, macro data, funds, IPOs, and full portfolio lifecycle management. Notable gaps remain, such as a basic company profile/ticker-resolution tool, dividend history, and analyst estimates, so it is not a perfect 5.

Resources