Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Fund Derivatives (a fund's N-PORT forwards, futures, swaps, options + counterparties)

fund_derivatives
Read-onlyIdempotent

Derivatives book for one fund (by SEC series_id, S000…) from its N-PORT filing: forwards (FX legs), futures, swaps (fixed rate / floating reference), options / swaptions / warrants and other derivatives. Returns net assets, the derivative value and its share of net assets, a by_type rollup (count, value, unrealized appreciation), the top 10 counterparties by gross value, and positions sorted by absolute value: counterparty, notional and currency, reference instrument, expiration, value_usd, unrealized appreciation and weight (a fraction of net assets).

Uses the fund's latest report on or before as_of; amendments (NPORT-P/A) are already applied. A fund with no derivatives returns empty lists and a no_derivatives warning. For the fund's bonds use tranche_fund_portfolio (include_noncusip=true adds loans, repos, cash and other positions without a CUSIP, and every call returns the asset mix).

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": {
      "series_id": "<series_id>"
    },
    "name": "fund_derivatives"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOnly return positions of this derivative type (the summaries still cover the whole book).
as_ofNoYYYY-MM-DD. Uses the fund's latest report on or before this date (default: latest).
limitNoPositions to return (default 100, max 2000).
series_idYesSEC series identifier (S000…) for the fund, e.g. S000016548 (PIMCO Income Fund).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/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 real behavioral context: the as-of resolution rule (latest report on or before the date, amendments applied) and the empty-result warning contract. It stops short of noting pagination/truncation behavior when the top-10 and by_type summaries coexist with a filtered position list, which is the only meaningful gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense paragraphs, entirely front-loaded: the resource and return payload come first, then the as-of/amendment and empty-result rules, then the sibling routing sentence. Every clause carries information — instrument taxonomy, rollup contents, sort order, weight definition — with no filler or 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?

There is no output schema, so the description carries the return-shape burden and does it in detail: summary fields, the by_type breakdown dimensions, counterparty aggregation, and per-position fields including weight expressed as a fraction of net assets. Combined with the as-of/amendment rule and the no-derivatives warning, an agent has everything needed to call this tool and interpret its response.

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 description coverage is 100%, and the schema itself already explains the type filter, the as_of date format and default, the limit default/max, and the S000 series_id convention with an example. The description corroborates as_of semantics and the fund scope but adds no format, unit, or interaction detail the schema does not already supply, so the baseline of 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?

The description names a specific verb and resource — the derivatives book for one fund from its N-PORT filing — and enumerates the instrument classes covered (forwards, futures, swaps, options/swaptions/warrants, other). It also states exactly what comes back (net assets, derivative value/share, by_type rollup, top-10 counterparties, sorted positions), so an agent can distinguish it from tranche_fund_portfolio without opening any schema.

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?

It gives an explicit routing rule: use tranche_fund_portfolio for the fund's bonds, reserving this tool for derivatives. It also discloses the edge case (a fund with no derivatives returns empty lists plus a no_derivatives warning) and notes amendments are already applied, so the agent knows what to expect and when not to reach for this tool.

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