Skip to main content
Glama

Treasury Auctions

sv_treasury
Read-only

US Treasury auction results — public domain (treasury_auctions panel). Params: limit. Free with X-ORKID-API-Key or $0.005 USDC/call via x402.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows, default 100, cap 500
panelNoPanel to query (default first). Available: treasury_auctions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld and non-destructive, so safety is covered. The description adds genuinely useful context beyond that: the data is public domain and access is free with an X-ORKID-API-Key or costs $0.005 USDC/call via x402. It still says nothing about result shape, sorting, or what happens when limit exceeds the cap.

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 compact sentences with the resource front-loaded and cost/auth trailing. The 'Params: limit' fragment carries little information beyond the schema, but overall there is no wasted prose.

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

Completeness3/5

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

For a simple two-parameter read tool with annotations and no output schema, the definition covers what the tool returns at a high level and how access is billed. It is missing any note on ordering, row semantics, or how auction records are shaped, which matters since no output schema exists to cover that.

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 both limit (default 100, cap 500) and panel fully documented in the schema. The description's 'Params: limit' and '(treasury_auctions panel)' merely restate the schema and add no syntax, format, or interpretation guidance.

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?

States the specific resource: 'US Treasury auction results', which is concrete enough to separate this from siblings like sv_futures or sv_macro on topic grounds. However, there is no explicit verb (list/retrieve) and no direct sibling differentiation, so an agent must infer it is a read/list endpoint from the annotations.

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

Usage Guidelines2/5

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

No when-to-use guidance is given, and no alternative is named. An agent cannot tell from the description whether Treasury auction data should come from this tool rather than sv_macro, sv_futures, or sv_facts when the boundary overlaps.

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