Skip to main content
Glama

equibles

by io.github.daniel3303

Company Debt Profile

GetDebtProfile
Read-only

Get a company's reported total debt history and its identified notes, loans, and revolving credit facilities. The latest 10-K establishes the annual baseline; each subsequent 10-Q and relevant 8-K updates 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

TableJSON Schema
NameRequiredDescriptionDefault
offsetNoZero-based instrument offset for paging (default 0, max 100000).
tickerYesStock ticker symbol (e.g., AAPL, MSFT).
maxResultsNoMaximum instruments to return (default 25, max 25).
evidenceOffsetNoZero-based character offset into the selected company-reported totals' exact evidence.
maxReportedTotalsNoMaximum company-reported totals to return (default 10, max 10).
reportedTotalOffsetNoZero-based company-reported-total offset for paging.
maxEvidenceCharactersNoMaximum 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. Dates show when Glama detected each change.

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

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses meaningful methodology: the latest 10-K establishes the annual baseline, 10-Q/8-K filings update durable instrument records rather than creating duplicates, and unmatched observations are disclosed and excluded. This gives the agent accurate expectations about deduplication and data coverage.

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?

The description is dense but every sentence carries distinct value: the core purpose, the deduplication behavior, and the pointer to the sibling tool. It is front-loaded with the main function and avoids repetition of schema content.

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?

With no output schema, the description compensates by stating what results contain: instrument summaries, IDs, reported totals history, and disclosed unmatched observations. It could go slightly further in describing the paging-related outputs, but the parameter schema already covers paging parameters and the description covers the key behavioral details.

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 the parameters are already well documented. The description adds context about output shape but does not add parameter-level meaning beyond what the input schema provides, so the baseline score of 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 names a specific verb and resource: get a company's reported total debt history and identified notes, loans, and revolving credit facilities. It clearly differentiates this from GetDebtInstrument by describing summary-level output with instrument IDs.

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 points to GetDebtInstrument for paged covenants, filing observations, exact evidence, and SEC exhibits, which tells an agent when to choose the sibling instead. It does not explicitly state when to prefer GetDebtProfile over related debt tools, but the intended use is clearly implied.

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