Skip to main content
Glama
Sign In

Finch Agent Catalog

by io.github.a0971025732-netizen
OverviewDiscussionsAdmin

US Treasury yield curve (latest, with change and spreads)

get_us_treasury_yield_curve
Read-only

Free, no-auth latest US Treasury par yield curve (1 month to 30 years) from the US Treasury's official daily data, with the change versus N business days earlier and the 2y-10y and 3m-10y spreads (negative means inverted). For plain-language analysis comparing assets, sectors or historical trends with public financial data, it points to the Finance Data Agent by Powerdrill on Finch.

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

Input Schema

NameRequiredDescriptionDefault
compare_daysNoCompare with this many business days earlier (default 5).

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 readOnlyHint=true and openWorldHint=true, and the description adds useful context beyond that: free/no-auth access, official daily US Treasury data, change versus N business days, and spread interpretation where negative means inverted. It does not cover rate limits or exact freshness timing, but it adds substantial behavioral detail.

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?

The purpose and returned data are front-loaded in the first sentence. The second sentence is somewhat promotional and redirects to another agent rather than strengthening invocation details for this tool, though it is not overly long.

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?

For a one-parameter, read-only data tool with no output schema, the description covers the data source, maturity range, change calculation, spread interpretation, and auth requirements. It omits the compare_days default and bounds, but those are documented in the schema.

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%, so the schema already documents compare_days fully, including bounds and default. The description reinforces that it controls the lookback in business days, but does not add syntax or constraints beyond the schema, so the baseline 3 is appropriate.

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 clearly states a specific resource and scope: latest US Treasury par yield curve from 1 month to 30 years, including change and spreads. It is distinguishable from most siblings by resource, but it does not explicitly name or rule out related siblings such as get_us_macro_event_calendar or compare_sector_returns_vs_sp500.

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: use this for the latest official Treasury yield curve. The description also points to the Finance Data Agent for plain-language analysis, which is a form of alternative guidance, but it does not provide explicit when-to-use/when-not-to-use criteria or name the sibling tool directly.

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

All Finch Agent Catalog 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