Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Corp Refi Screen (issuers ranked by debt maturing in year)

tranche_refi_screen
Read-onlyIdempotent

Cross-sectional refi-pressure screener: corporate issuers ranked by fund-held debt value maturing in a target year, as-of a date. Returns issuer ticker/cik + fund_held_value + weighted_coupon + bond_count, descending. The 'who has the biggest 2027 wall' question. Source: N-PORT-P fund holdings panel.

IMPORTANT: This is the FUND slice of total maturing debt — N-PORT-P covers ~$3T of ~$11T US corp bonds. Honest as a RANK (within-panel ordering is load-bearing); do NOT present absolute $ as 'total debt maturing.' Corporate-only (issuer_cat='CORP'). Historical depth: 2019-09-30 to current — pin as_of to any quarter-end for backtests.

Console Credit Monitor rules: defaults to the newest SETTLED month (the newest month is still filling in); weighted_coupon above 20% is blanked (structured notes). Each issuer carries listed_parent {ticker, cik, name, via} — the listed company behind a financing sub, resolved via bond CIK, MARS company CIK, Ex-21 parent, then normalised name.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "maturity_year": "<maturity_year>"
    },
    "name": "tranche_refi_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoReport date YYYY-MM-DD (default: the newest settled month).
top_nNoMax issuers to return (default 25, max 200).
maturity_yearYesYear bonds mature in (e.g. 2027).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover the read-only/idempotent safety profile, and the description adds substantial behavior beyond that: N-PORT-P covers roughly $3T of ~$11T US corp bonds so rankings are load-bearing but absolutes are not, defaults to the newest SETTLED month because the current month is still filling in, weighted_coupon above 20% is blanked as structured notes, and listed_parent is resolved through a documented four-step chain. This is exactly the kind of caveat an agent cannot infer from structured fields.

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?

Long for a three-parameter tool, but front-loaded with the purpose and the return shape, then segmented into labeled blocks (IMPORTANT, historical depth, Console Credit Monitor rules) so each caveat is scannable. Nearly every sentence carries load-bearing information about interpretation limits.

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?

There is no output schema, and the description compensates by naming the returned fields and their ordering, plus the coverage caveat that governs how those numbers may be presented. For a screening tool with three parameters, nothing an agent needs in order to call it or report results responsibly is missing.

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 real meaning: as_of can be pinned to any quarter-end for backtests and defaults to the newest settled month, and maturity_year is framed as a debt-wall year. top_n is left entirely to the schema, which caps the score below 5.

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 states a specific verb and resource ('cross-sectional refi-pressure screener: corporate issuers ranked by fund-held debt value maturing in a target year'), names the returned fields, and characterizes the question it answers ('who has the biggest 2027 wall'). An agent can distinguish this ranking screen from issuer-level siblings like tranche_issuer_debt on the fund-slice framing alone.

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?

It gives a clear use case ('the who has the biggest 2027 wall question'), an explicit scope restriction (corporate-only, issuer_cat='CORP'), a validity window for backtests (2019-09-30 to current, pin as_of at quarter-end), and a strong negative instruction not to present absolute dollars as total debt maturing. It does not name a specific alternative tool to use instead when the fund slice is insufficient, which keeps it from 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