Skip to main content
Glama
Sign In

SpreadBench NCSX-IS — AI Infrastructure Bond Issuance Spread Index

by com.spreadbench
OverviewDiscussionsAdmin

ncsx_stories

Read-onlyIdempotent

Citable data stories (editorial layer) recomputed live from the same public data as the index, each with headline numbers, bilingual page URLs and a ready-to-post 1200x630 share card: (1) the maturity wall of the peak year; (2) the CoreWeave repricing — every CoreWeave bond widened 191-258bp between issuance and the latest N-PORT fund marks (2026-08-31) while same-sector peers (GLXY / CORZ / CIFR) moved only 17.6-40.7bp. Returns numbers computed from current universe + marks data, not cached text. Facts only — no ratings, no investment advice.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: values are recomputed live from the current universe and marks data rather than cached text, and each story ships with bilingual page URLs and a 1200x630 share card. It does not describe latency or rate limits, but it does clarify data freshness and output payload shape.

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

Conciseness3/5

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

The core purpose is front-loaded and the numbered list makes the two stories scannable. But the description spends substantial length on precise figures (191-258bp, 17.6-40.7bp, a specific 2026-08-31 marks date) that are story content rather than routing information, which dilutes the definition.

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 parameters and no output schema, the description carries the return-value burden and does so: headline numbers, bilingual page URLs, share card dimensions, and live recomputation provenance. It is essentially complete for a no-arg retrieval tool, with only explicit sibling differentiation 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?

The tool takes zero parameters, which is the baseline-4 case: there is nothing for the description to disambiguate. It also implicitly explains the no-argument behavior by enumerating the fixed set of stories returned.

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 names a specific resource — citable data stories with headline numbers, bilingual page URLs and a share card — and enumerates the two exact stories returned (maturity wall of the peak year; CoreWeave repricing vs peers). That is concrete enough to predict the output, but it never contrasts itself with siblings like ncsx_facts or ncsx_latest, so an agent must infer the boundary.

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 'citable' and 'ready-to-post share card', which suggests citing or publishing, and the 'facts only — no ratings, no investment advice' line sets a constraint on use. However, there is no explicit when-to-use statement and no named alternative for agents who just want raw figures (e.g., ncsx_facts, ncsx_latest).

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