Skip to main content
Glama

Industry Rate Environment, Trends

rate_environment_trends
Read-only

Treasury yield-curve history plus the industry-wide NIM / yield / funding-cost trend. (Source: FRED Treasury yield curve + FFIEC Call Report.)

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

Input Schema

NameRequiredDescriptionDefault
yield_curve_limitNoMax yield-curve observations (1-2000, default 500).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-data profile is covered. The description adds genuinely useful provenance (FRED Treasury yield curve + FFIEC Call Report), but says nothing about freshness, latency, coverage period, or units for NIM/funding cost.

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

Conciseness5/5

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

Two tight sentences with zero waste: content first, source provenance second in a parenthetical. Nothing is redundant or buried.

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-optional-parameter, read-only, no-output-schema tool, the description covers what is returned and where the data comes from. The remaining gap is not specifying the trend window or units, which an agent might need to interpret results.

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% and the single optional parameter yield_curve_limit is fully documented in the schema, so the baseline is 3. The description adds no further meaning about how the limit affects the returned series.

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 a specific resource and scope: Treasury yield-curve history plus industry-wide NIM/yield/funding-cost trend. An agent can tell this is an industry-aggregate rate/margin dataset rather than a single-bank view. It does not explicitly contrast itself with the sibling rate_environment, so it falls short of the top score.

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?

There is no explicit statement of when to use this tool versus rate_environment or the various industry_* trend siblings. The only hint is the phrase 'industry-wide ... trend', which implies aggregate rather than institution-level queries, but the agent must infer that distinction.

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