Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Widest-Held Corp Bonds (most-owned by N-PORT-P funds)

tranche_widest_held
Read-onlyIdempotent

Most widely fund-held corporate bonds at an as-of date, ranked by number of distinct funds holding the bond. Returns CUSIP, issuer ticker, total fund-held value, n_funds, and consensus mean price. Source: N-PORT-P fund holdings panel.

IMPORTANT: 'Widely held' = held by the most N-PORT-P registered funds (mutual funds + ETFs). Insurers, pensions, foreign holders are NOT counted. Use as a sample of broad-market ownership, not absolute breadth. Corporate-only (issuer_cat='CORP'). Historical depth: 2019-09-30 to current.

Each bond also carries coupon (blanked above 20% — structured notes), maturity_date, est_yield_pct, is_distressed (est. yield >= 12% or price < 50, structured issuers excluded), is_disputed (price std dev >= 5 pts across 3+ funds) and listed_parent {ticker, cik, name, via} (Console Credit Monitor rules).

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

Input Schema

NameRequiredDescriptionDefault
as_ofNoReport date YYYY-MM-DD (default: latest from pipeline_meta).
top_nNoBonds to return (default 50, max 200).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds substantial context beyond them: source panel, historical depth boundary (2019-09-30 to current), ranking semantics, the coverage caveat about which holder types are excluded, and field-level rules for derived values (coupon blanked above 20%, is_distressed and is_disputed thresholds, listed_parent provenance). This is exactly the kind of disclosure an agent needs to interpret output correctly.

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?

Purpose and ranking semantics are front-loaded in the first sentence, and the IMPORTANT block correctly isolates the definitional caveat. The final paragraph is a dense run-on catalog of per-bond fields, but since no output schema exists each item carries informational value.

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?

With no output schema, the description takes on the burden of describing return fields and does so thoroughly: CUSIP, issuer ticker, total fund-held value, n_funds, consensus mean price, plus coupon, maturity_date, est_yield_pct, and the flag/derived fields. Historical depth and source are also stated, leaving nothing material for a correct call or interpretation.

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 coverage is 100%, with both as_of (YYYY-MM-DD, default latest from pipeline_meta) and top_n (default 50, max 200) fully documented in the schema. The description only implies an 'as-of date' and adds no format, default, or bound details of its own, so the baseline 3 applies.

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+resource (rank most widely fund-held corporate bonds by number of distinct funds holding) plus scope qualifiers: as-of date, corporate-only via issuer_cat='CORP', and N-PORT-P source. That scope statement is what separates it from a single-bond holder lookup like tranche_bond_holders, so an agent can pick it without opening a schema.

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?

Gives explicit interpretive guidance ('Use as a sample of broad-market ownership, not absolute breadth') and explicitly excludes what is NOT counted (insurers, pensions, foreign holders), which prevents misuse of the ranking as absolute breadth. It does not name a specific alternative tool or the condition that would send the agent elsewhere, so it stops short of a 5.

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