Skip to main content
Glama
Sign In
Market Intelligence MCP

Market Intelligence MCP

Official
by BullrunData
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

interest_rates

Read-only

Retrieve current interest rates including Fed funds, 2Y/5Y/10Y/30Y Treasury yields, 3M T-Bill, prime rate, and 30-year and 15-year mortgage rates.

Instructions

Get current interest rates: Fed funds, 2Y/5Y/10Y/30Y Treasury yields, 3M T-Bill, prime rate, 30-year and 15-year mortgage rates.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description doesn't need to repeat safety info. It adds context by listing specific rates returned, but no behavioral traits like data freshness or potential delays.

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?

Single sentence of 23 words, front-loaded with the action, no redundancy. Every word serves a purpose.

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 simple zero-parameter tool, listing all returned rates provides adequate completeness. Missing details on data source or update frequency, but still functional for agent use.

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?

With no parameters (100% schema coverage), the description adds value by enumerating the output fields, helping the agent understand what data will be retrieved beyond the empty schema.

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

Purpose5/5

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

The description clearly states the tool retrieves current interest rates and lists specific rates (Fed funds, Treasury yields, T-Bill, prime, mortgages), distinguishing it from sibling tools like yield_curve or inflation_data.

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 guidance on when to use this tool versus siblings like yield_curve or economic_indicator. The description provides no context for selection, leaving the agent to infer from the listed rates.

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

Deploy Server

Other Tools