Equibles

Company Debt Profile

GetDebtProfile

Read-only

Get a company's source-linked reported debt balances, total debt history, and identified notes, loans, and revolving credit facilities. The latest annual report establishes the baseline; subsequent interim reports and event disclosures update durable instrument records instead of creating a new instrument from a similar-looking row. Results summarize each instrument and provide its ID; use GetDebtInstrument for paged covenants, filing observations, exact evidence, and governing SEC exhibits. Unmatched observations are disclosed and excluded.

Input Schema

Name	Required	Description
`offset`	No	Zero-based instrument offset for paging (default 0, max 100000).
`ticker`	Yes	Stock ticker symbol (e.g., AAPL, MSFT), or MIC:TICKER (e.g., XPAR:AIR) for a listing outside the US.
`maxResults`	No	Maximum instruments to return (default 25, max 25).
`evidenceOffset`	No	Zero-based character offset into the selected company-reported totals' exact evidence.
`maxReportedTotals`	No	Maximum company-reported totals to return (default 10, max 10).
`reportedTotalOffset`	No	Zero-based company-reported-total offset for paging.
`maxEvidenceCharacters`	No	Maximum exact-evidence characters to return for the selected company-reported totals (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."

Changed5 schema fields changedSep 4, 2026

addedInput schema / properties / evidenceOffset

Added value: +{
+  "default": 0,
+  "description": "Zero-based character offset into the selected company-reported totals' exact evidence.",
+  "type": "integer"
+}

addedInput schema / properties / maxEvidenceCharacters

Added value: +{
+  "default": 0,
+  "description": "Maximum exact-evidence characters to return for the selected company-reported totals (default 0, max 12000). Use a positive value to read evidence losslessly in character pages.",
+  "type": "integer"
+}

addedInput schema / properties / maxReportedTotals

Added value: +{
+  "default": 10,
+  "description": "Maximum company-reported totals to return (default 10, max 10).",
+  "type": "integer"
+}

changedInput schema / properties / maxResults / description

Previous value: -"Maximum instruments to return (default 25, max 500)."New value: +"Maximum instruments to return (default 25, max 25)."

addedInput schema / properties / reportedTotalOffset

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

AddedSep 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuine behavioral context beyond that: the annual-report baseline, that interim reports update durable instrument records rather than duplicating, and that unmatched observations are disclosed but excluded. It stops short of describing pagination/return-size behavior, so a 4 rather than 5.

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?

Three sentences, front-loaded with purpose, then data-update semantics, then sibling routing. Dense but every clause earns its place; minor density in the middle sentence keeps it from a 5.

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?

No output schema exists, but the description summarizes the return shape ('Results summarize each instrument and provide its ID'). Combined with full schema coverage and annotations covering safety, the definition is nearly complete; only explicit paging/evidence-reading guidance is left implicit.

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%, so all seven paging/evidence parameters are already documented in the schema. The description adds no parameter-level syntax or format detail; the baseline 3 applies when the schema does the heavy lifting.

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 a company's source-linked reported debt balances, total debt history, and identified notes, loans, and revolving credit facilities') and explicitly distinguishes itself from the sibling GetDebtInstrument. An agent can tell what this tool returns without opening the schema.

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?

Names the alternative tool and the exact condition for using it: 'use GetDebtInstrument for paged covenants, filing observations, exact evidence, and governing SEC exhibits.' This is explicit when-to-use routing, not inference.

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