Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Debt Flow Movers (issuers funds are fleeing / piling into)

tranche_debt_flow_movers
Read-onlyIdempotent

Market-wide: the issuers whose corporate bonds funds are FLEEING (direction='outflow', the credit-distress feed) or PILING INTO ('inflow') in one month, ranked by net fund flow in USD. Console Credit Monitor rules: reads mars.tranche_issuer_flow_v2; defaults to the newest month whose issuer coverage is at least 85% of the prior month's (a month still filling in is skipped — month_choice says which month was used and why); only issuers with $50M+ of fund-held bonds (min_issuer_value_usd). Each row: issuer cik / ticker / name, listed_parent {ticker, cik, name, via}, net_flow_usd, net_flow_pct, n_continuing_funds, total fund-held value, small_basis (< 20 continuing funds). Rows marked 'warn' by tranche (tiny bases, median 2 funds) are left out unless include_warns=true.

How to read it: net_flow_usd is quarter-over-quarter (N-PORT holdings are quarterly per fund) and coverage-immune — it sums, over funds that held the issuer's bonds at both this report and that fund's OWN prior report, the change in value; which other funds filed doesn't matter, so it measures real trading, not the staggered-filing sawtooth. Negative = existing holders net-trimming (outflow), positive = net-adding. n_continuing_funds is the basis: it swings with the fiscal calendar (~600 funds at a calendar quarter-end, ~15 on odd fiscal dates), so prefer net_flow_pct for comparisons and distrust pct on small bases. Fund-held only (N-PORT-P, a ~$3T sample of registered funds), corporate bonds only.

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_debt_flow_movers"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoReport date YYYY-MM-DD (default: newest month with >= 85% of the prior month's issuer coverage).
top_nNoRows (default 25, max 200).
directionNooutflow
min_fundsNoMinimum continuing funds (default 1; rows under 20 carry small_basis=true).
include_warnsNoInclude rows tranche marks 'warn' (tiny bases).
min_issuer_value_usdNoMinimum fund-held value of the issuer's bonds (default $50M).

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 read-only/idempotent annotations, the description discloses the source table, the default month-selection rule with 85% coverage, the $50M minimum issuer value filter, warn-row exclusion behavior, and how net_flow_usd is computed. It also explains why net_flow_usd is coverage-immune and how n_continuing_funds affects interpretation.

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 definition is front-loaded with the core purpose and then structured into a 'How to read it' section. It is dense and parenthetical in places, but most sentences carry useful interpretation or caveats rather than repetition.

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 six-parameter, read-only market screener with no output schema, the description is complete: it covers source data, default month logic, filters, row fields, warn handling, interpretation caveats, and the fund-held corporate-bond universe. An agent has enough context to invoke and interpret the tool 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 description coverage is high at 83%, but the description still adds meaning: direction maps to outflow as the credit-distress feed, as_of is tied to month_choice and the 85% coverage rule, include_warns controls warn-row inclusion, and min_issuer_value_usd is explained in context. It does not add much beyond the schema for top_n.

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 states a specific verb and resource: it identifies issuers whose corporate bonds funds are fleeing or piling into, ranked by net fund flow in USD. The 'Market-wide' scope helps distinguish it from issuer-level siblings, but it does not explicitly name an alternative or state a brother tool's role.

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 'Market-wide' and by the direction options outflow/inflow, plus extensive guidance on how to read the output. However, it does not explicitly say when to use this tool versus sibling tools such as tranche_issuer_debt_flow or tranche_issuer_debt.

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