Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Capital Structure (market cap to EV, leverage, coverage, 8 quarters)

capital_structure
Read-onlyIdempotent

A company's capital structure: share price, cover-page shares outstanding (with the filing they come from), market cap, short- and long-term debt, cash, operating leases and enterprise value; trailing-twelve-month revenue, EBIT, EBITDA, interest expense, net income and free cash flow; leverage (debt / EBITDA, net debt / EBITDA, debt / equity) and interest coverage (EBIT / interest, EBITDA / interest); EV / revenue, EV / EBIT, EV / EBITDA. Plus history — the same figures at each of the last 8 quarter ends — and recent_debt_issuance (notes and loans announced in 8-K Item 2.03, with rate and maturity; each row carries accession + filing_url of its 8-K). Same data as Kaleidoscope Console's Capital Structure report.

Banks, brokers and insurers (SIC 6000-6499) get book value, price / book, ROE and ROA instead of EV and leverage (is_financial).

Rules: TTM sums the last 4 reported quarters; year-to-date or full-year figures filed under a quarter label are converted to the quarter (listed in adjusted_fields). EBITDA = EBIT + D&A and is null when D&A is not tagged. EV = market cap + total debt - cash; preferred stock and minority interest are shown but not added (as in Console); ev_incl_leases adds operating lease liabilities. An ADR's market cap uses the ordinaries-per-ADS ratio. For filers reporting in another currency, EV and the EV multiples are null (market cap is USD, the balance sheet is not); ratios that do not mix currencies stay. checks flags a market cap that moved much more than the share price between quarters — a spin-off, reverse split the price data does not adjust for, or a share-count error; read the filing before relying on that quarter. as_of gives the picture on a past date using only filings and prices known then.

atm_usage (#2189): at-the-market program use from the 10-Q / 10-K — selling_now (sold in one of the last two reported quarters), the last quarter's shares sold, net proceeds, remaining capacity, sales agents, quote + accession as evidence, and a quarterly history; null when the company has no ATM on file.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "capital_structure"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoYYYY-MM-DD — point in time. Default today.
company_idNomars company UUID (instead of ticker_or_cik).
ticker_or_cikNoTicker or CIK. For multi-class companies the ticker picks the price used (all classes' shares are counted).
history_quartersNoQuarter ends in `history` (0-12).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the derivation rules that determine whether values are present: TTM summation with YTD-to-quarter conversion in `adjusted_fields`, EBITDA null when D&A is untagged, EV exclusions for preferred and minority interest, `ev_incl_leases`, ADR share-ratio handling, and currency-mixing nulls. It also explains the `checks` flag as a data-quality warning pointing to spin-offs, splits or share-count errors.

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?

The payload inventory is front-loaded, then separated into a clearly labeled 'Rules:' block and a dedicated `atm_usage` paragraph, which makes it navigable despite its length. Some formula restatements (EBITDA = EBIT + D&A, EV = market cap + debt - cash) are arguably more than an agent needs, keeping it from a 5.

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 computed-metrics tool with four optional parameters and no output schema, the description covers definitions, edge cases, null conditions, financial-firm substitution and provenance (`accession`/`filing_url`), which is everything needed to call it and interpret gaps correctly.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: `as_of` is not merely a date but restricts inputs to filings and prices known at that time, and the ticker choice interacts with multi-class pricing and ADR ratios. `history_quarters` and `company_id` add nothing beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates exactly what the tool returns — share price, shares outstanding, market cap, debt, cash, EV, leverage and coverage ratios, EV multiples, plus `history`, `recent_debt_issuance` and `atm_usage` — so there is no ambiguity about the resource. It does not, however, distinguish itself from siblings such as company_private_capital, leaving the agent to infer the boundary.

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

Usage Guidelines3/5

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

Usage is implied by the payload inventory and by notes like '`as_of` gives the picture on a past date' and 'null when the company has no ATM on file', which tell the agent when certain outputs appear. There is no explicit when-to-use/when-not statement or routing to an alternative tool for adjacent data.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources