Skip to main content
Glama
Sign In

SpreadBench NCSX-IS — AI Infrastructure Bond Issuance Spread Index

by com.spreadbench
OverviewDiscussionsAdmin

ncsx_filings

Read-onlyIdempotent

SEC filing radar for the 9 AI-infrastructure issuers covered by SpreadBench (6 in NCSX-IS plus Nebius, IREN and Hut 8 on the watchlist): every filing from the last 45 days, noise forms (ownership, routine) filtered out, pricing-chain forms (FWP, 424B*, S-3*, F-10) flagged with pricing_signal=true, each row linked to the EDGAR original. NCSX-IS is event-driven, so a new pricing-chain filing is what triggers an index re-version — use this to check whether a re-version is coming.

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

Input Schema

NameRequiredDescriptionDefault
formNoOptional filter: exact SEC form type (e.g. "8-K", "10-Q", "424B5"). Omit to get all forms.
issuerNoOptional filter: issuer name or ticker, case-insensitive substring (e.g. "CoreWeave", "WULF", "Hut 8"). Omit to get all issuers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the bar is lower, and the description still adds real behavior: a fixed 45-day window, noise-form suppression, pricing_signal flagging, and a link to the EDGAR original for each row. It does not cover result ordering, pagination, or what happens when filters exclude everything.

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?

Two sentences, front-loaded with the resource and scope, then the actionable re-version signal. The coding is dense (NCSX-IS, SpreadBench, pricing-chain) but each clause carries information; no filler sentences.

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

Completeness4/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 does the job of describing returns: rows per filing, a pricing_signal flag, and an EDGAR link. It is nearly self-sufficient for a two-optional-param read tool, though it omits the remaining row fields and whether the 45-day window is fixed.

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%, so both filters (form, issuer) are already fully documented, which sets the baseline at 3. The mention of FWP, 424B*, S-3* and F-10 is useful domain vocabulary for choosing form values, but it does not explain how filtering interacts with the built-in noise removal or the 45-day window.

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 the exact resource (SEC filings for 9 AI-infrastructure issuers), the scope (last 45 days, noise forms removed), and the distinguishing feature (pricing-chain forms flagged with pricing_signal=true). An agent can tell this apart from siblings like ncsx_constituents or ncsx_latest without opening the 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?

It gives an explicit trigger for use: since NCSX-IS is event-driven, a new pricing-chain filing is what triggers re-version, so call this to check whether one is coming. It stops short of naming an alternative tool or stating when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SpreadBench NCSX-IS — AI Infrastructure Bond Issuance Spread Index toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources