BrinkerAdvisor Rates

Rates explorer

compare_rates

Create a bounded side-by-side comparison for an explicit comparison or contrast of current CD, money-market, Treasury, or municipal options with instrument and maturity filters. Returns applied filters, current options, and comparability limitations without selecting a winner. Every option contains a canonical brinkeradvisor_url and an original source_name and source_url. A request merely to find or list several matching records is outside this tool's comparison intent. Economic or Federal Reserve forecasts, account actions, personalized advice, tax advice, and suitability are outside this tool's scope.

Input Schema

Name	Required	Description	Default
`limit`	No
`instrument_types`	No
`maximum_term_months`	No
`minimum_term_months`	No

Output Schema

Name	Required	Description
`as_of`	Yes	Feed publication date; each option has its own record date and age.
`options`	Yes
`applied_filters`	Yes
`source_freshness`	Yes	Feed age band, not the age of every option.
`comparison_limitations`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 18, 2026
- removedOutput schema / properties / options / items / properties / term_months / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / options / items / properties / term_months / type
```
Added value: +[
+  "number",
+  "null"
+]
```
Changed2 schema fields changedOct 9, 2026
- addedInput schema / properties / instrument_types / default
```
Added value: +[
+  "cd",
+  "money_market",
+  "treasury",
+  "municipal"
+]
```
- removedInput schema / required
```
Removed value: -[
-  "instrument_types"
-]
```

Changed2 schema fields changedOct 4, 2026

changedOutput schema / properties / options / items / properties / brinkeradvisor_url / description

Previous value: -"Absolute canonical BrinkerAdvisor record URL. The final answer must display this URL as a clickable link."New value: +"Absolute canonical BrinkerAdvisor record URL, distinct from the original provider source URL."

changedOutput schema / properties / options / items / properties / source_url / description

Previous value: -"Absolute original provider or government source URL. The final answer must distinguish this provenance link from the BrinkerAdvisor record link."New value: +"Absolute original provider or government source URL documenting the record's provenance."

Changed5 schema fields changedOct 3, 2026

addedOutput schema / properties / as_of / description

Added value: +"Feed publication date; each option has its own record date and age."

addedOutput schema / properties / options / items / properties / as_of

Added value: +{
+  "description": "Original record value date, which may precede the feed publication date.",
+  "type": "string"
+}

addedOutput schema / properties / options / items / properties / data_age_hours

Added value: +{
+  "anyOf": [
+    {
+      "minimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Age of this record, not the feed, when retrieved."
+}

changedOutput schema / properties / options / items / required

Previous value: -[
-  "id",
-  "instrument_type",
-  "issuer_or_institution",
-  "product",
-  "term",
-  "term_months",
-  "published_yield",
-  "source_name",
-  "source_status",
-  "source_url",
-  "brinkeradvisor_url"
-]New value: +[
+  "id",
+  "instrument_type",
+  "issuer_or_institution",
+  "product",
+  "term",
+  "term_months",
+  "published_yield",
+  "as_of",
+  "data_age_hours",
+  "source_name",
+  "source_status",
+  "source_url",
+  "brinkeradvisor_url"
+]

addedOutput schema / properties / source_freshness / description
```
Added value: +"Feed age band, not the age of every option."
```

First observedOct 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, destructiveHint=false. The description adds real context beyond them: what is returned (applied filters, current options, comparability limitations), that no winner is selected, and that each option carries a canonical brinkeradvisor_url plus original source_name/source_url. It does not explain the side effects implied by the non-read-only, non-idempotent hints, which is the one remaining ambiguity.

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?

Purpose, output contents, and exclusions are front-loaded in a useful order, and the density is justified by the tool's breadth. It is longer than needed at the tail, where two separate sentences restate that things are outside the tool's scope, and the closing exclusion list is somewhat enumerative.

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?

An output schema exists, so return-value details are optional, yet the description still summarizes the payload (applied filters, options, comparability limitations, attribution URLs), which is helpful. Scope and exclusions are thorough. The only material gap is the undocumented limit parameter, given 0% schema coverage.

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 0%, so the description must carry parameter meaning, and it only partly does: 'instrument and maturity filters' loosely maps to instrument_types and the two term-months bounds. The limit parameter (1-20, default 10) is never mentioned, nor are units or inclusive/exclusive bounds for the term range.

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 gives a specific verb and resource: 'Create a bounded side-by-side comparison' of four named instrument classes with instrument and maturity filters. It explicitly excludes a use case ('a request merely to find or list several matching records is outside this tool's comparison intent'), which separates it from listing-style siblings like search. An agent can identify the tool's job without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

When-to-use is explicit ('an explicit comparison or contrast' request) and when-not is well covered (find/list requests, economic or Fed forecasts, account actions, personalized advice, tax advice, suitability). It never names the alternative sibling tools (search, mention_rates, build_ladder) that should handle the excluded cases, so routing is inferable rather than stated.

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

All BrinkerAdvisor Rates 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?