tollbooth

treasury_dts

Treasury DTS TGA — operating_cash_balance free gov public-domain, TGA close $B d/d delta, deposits/withdrawals enrichment. Liquidity / debt-ceiling / SPX direction edge, 2nd upstream.

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

Input Schema

Name	Required	Description	Default
`days`	No	Days back, default 7
`min_score`	No	Min score

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 11, 2026

TDQS

D1.9/5.0

Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It mentions 'free gov public-domain' but does not state that the tool is read-only, discuss authentication needs, rate limits, or any side effects. The behavioral profile is largely opaque.

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

Conciseness2/5

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

The description is short but poorly structured, using fragmented phrases that are hard to parse. It sacrifices clarity for brevity and does not earn its place as a coherent guide.

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

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description should explain what the tool returns (e.g., a number, time series, etc.). It only hints at concepts like 'operating_cash_balance' and 'd/d delta' but does not give a complete picture. This is insufficient for an agent.

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% with descriptions for both parameters ('days' and 'min_score'). The tool description does not add meaningful semantic value beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is cryptic and jargon-heavy, using abbreviations like 'TGA', 'd/d delta', and '2nd upstream' without explanation. It fails to clearly state what the tool does in simple terms, making it hard for an agent to infer its purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus siblings like 'national_debt' or 'fred_series'. The description lacks any context about suitability or alternatives.

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

All tollbooth tools Inspect

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

Need Help?