RateSonar MCP

rate_details

Read-onlyIdempotent

Exact CDR product-reference detail for one institution and product: every published lending or deposit rate entry and tier, with fees, features, eligibility, constraints, source quality flags, the date the version was recorded and the lender's own links. asOf returns the version current on that date. Detail exists for CDR products from 2026-06-12; it holds the conditions a headline rate leaves out.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "institutionId": "<institutionId>",
      "productId": "<productId>"
    },
    "name": "rate_details"
  }
}

Input Schema

Name	Required	Description
`asOf`	No	Latest snapshot on or before YYYY-MM-DD. Optional.
`productId`	Yes	CDR product id.
`institutionId`	Yes	Institution id, e.g. "nab".

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that: data coverage begins 2026-06-12 and asOf resolves to the version current on a given date, which materially affects how the agent should call it.

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?

Three sentences, front-loaded with the core verb and scope, then the snapshot rule and the coverage caveat. The middle enumeration of returned fields is a long run-on that could be tightened, but it carries information and no sentence is wasted.

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?

With no output schema, the description usefully enumerates what is returned (rates, tiers, fees, features, eligibility, constraints, source quality flags, dates, lender links) and flags the 2026-06-12 data start. It omits edge behavior such as an asOf before the coverage start or a not-found product, which is a minor gap for a read-only lookup.

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%, so both required ids and asOf are already documented in the schema. The description's gloss on asOf ('returns the version current on that date') largely restates the schema's 'Latest snapshot on or before YYYY-MM-DD' and adds little parameter-level meaning, so the baseline 3 applies.

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 states a specific verb+resource: retrieving exact CDR product-reference detail (every rate entry and tier) for one institution and product. It clearly distinguishes a single-product detail lookup from aggregate/temporal siblings, though it never names a sibling like rate_history or compare_rates explicitly.

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 by the required institutionId/productId focus and the asOf snapshot semantics, but there is no explicit when-to-use/when-not-to-use guidance and no routing to alternatives such as rate_history or rate_changes. An agent must infer the boundary from the sibling names alone.

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

All RateSonar MCP tools Inspect

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

Need Help?