Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

BDC Summary (every public BDC side by side: mark, below-90 share, non-accruals, NAV)

bdc_summary
Read-onlyIdempotent

Every covered public BDC side by side at its latest quarter (Console Credit Monitor BDC table): debt fair value, amortized cost, mark % (FV / cost), share of FV marked below 90% of cost, non-accrual % by FV and by cost, NAV per share, borrower count, as-of quarter. From each BDC's 10-Q Schedule of Investments (53 BDCs, data through 2026-09-30; e.g. ARCC, BCRED, OBDC, FSK, BXSL).

Source-gap flag: a book of 100+ borrowers reporting zero non-accruals is almost always an extraction miss, so non-accrual % comes back null with non_accrual_source_gap=true — never read it as 0%. BDCs report on staggered quarters; report_date is per BDC. For one BDC's positions, seniority mix and trend call credit_bdc_loan_book(ticker); for shared loans marked differently across BDCs, credit_cross_held_loans.

Params: tickers (subset), as_of (latest quarter on or before), sort (fv_desc default / mark_asc / below_90_desc / non_accrual_desc). Each row carries accession + filing_url (the BDC's 10-Q/10-K for nav_report_date, the same quarter's filing as the marks when nav_report_date = report_date; open with get_filing).

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": "bdc_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNofv_desc
as_ofNoYYYY-MM-DD: each BDC at its latest quarter on or before this date.
tickersNoOnly these BDC tickers (default all covered).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. Beyond that, the description adds genuinely useful behavior: null non-accrual values are flagged via non_accrual_source_gap=true and must not be read as 0%, and BDCs report on staggered quarters so report_date is per BDC. A 3 rather than higher because the source-gap and staggering notes, while valuable, are the only behavioral disclosures and no volume or latency characteristics are given.

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?

Structure is strong—the core capability is front-loaded in bold, followed by a distinct behavioral caveat block and then params. Some density creeps in (the parenthetical FV/cost restatement, the long filing_url aside) that could be tightened without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because there is no output schema, the description carries the burden of explaining return values, and it does enumerate the row fields, so an agent knows what comes back. However, nothing is said about row count, pagination, or how to handle BDCs with missing quarters when as_of predates coverage, which leaves real gaps for a cross-company table tool.

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 67%, and the description reinforces each param's meaning: tickers as a subset (default all covered), as_of as the latest quarter on or before the date, and sort's default fv_desc plus the alternative enum values, including the non-obvious mark_asc/below_90_desc/non_accrual_desc orderings. It adds modest clarity beyond the schema but does not define each sort key's exact ordering semantics.

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?

Opens with a specific, bolded statement of what the tool returns: every covered public BDC side by side at its latest quarter, then enumerates the exact columns (debt fair value, amortized cost, mark % = FV/cost, below-90 share, non-accrual % by FV and cost, NAV/share, borrower count, as-of quarter). It also names the source (10-Q Schedule of Investments), the universe (53 BDCs, through 2026-09-30), and distinguishes itself from credit_bdc_loan_book and credit_cross_held_loans.

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?

Gives explicit routing conditions to siblings: call credit_bdc_loan_book(ticker) for a single BDC's positions, seniority mix and trend, and credit_cross_held_loans for shared loans marked differently across BDCs. It also tells the agent to open the per-row accession/filing_url with get_filing, so the cross-tool workflow is spelled out rather than inferred.

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