Skip to main content
Glama

Deposit Rates

rates_deposit
Read-onlyIdempotent

National deposit rate series. (Source: BankRegReports.)

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

Input Schema

NameRequiredDescriptionDefault
product_codeNoDeposit product code, e.g. CD_24_MONTH.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description's only added behavior detail is source attribution (BankRegReports); it says nothing about freshness, historical depth, granularity, or what happens when product_code is omitted.

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 short sentences, front-loaded with the resource scope, with no filler. The brevity is appropriate, though the parenthetical source note is the only content in the second sentence and carries little decision value.

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

Completeness2/5

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

With no output schema, the description should convey the shape of a "series" — time coverage, frequency, units, and behavior of the optional filter. None of that is present, leaving the agent unable to predict what it will receive or how to phrase a request.

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 carries its own example (CD_24_MONTH), so the schema does the documentation work. The description adds no meaning beyond it — notably it does not explain what the default result is when product_code is not supplied.

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

Purpose3/5

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

The description names the resource and its scope ("National deposit rate series"), so an agent knows it retrieves national-level deposit rates. However, it does not distinguish this from siblings such as rates_national or rates_consumer, and it never states the verb (list/retrieve) or what a "series" contains.

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 guidance on when to use this tool, when not to, or which sibling covers related rate data (consumer, mortgage, treasury bill). The agent must infer from the name alone, and with many rate siblings that inference is unreliable.

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