BrinkerAdvisor Rates

Build an illustrative fixed-income ladder

build_ladder

Build an educational equal-weight maturity ladder from current eligible public CD, money-market, Treasury, or municipal options for a requested rung count and term range. Every covered rung contains a canonical brinkeradvisor_url and an original source_name and source_url. Returns explicit uncovered rungs. This tool does not access accounts, trade, recommend a product, forecast rates or the economy, or provide suitability or tax advice.

Input Schema

Name	Required	Description	Default
`rung_count`	Yes
`instrument_types`	Yes
`maximum_term_months`	Yes
`minimum_term_months`	Yes
`hypothetical_amount_usd`	No

Output Schema

Name	Required	Description
`as_of`	Yes	Feed publication date; each covered rung has its own record date and age.
`rungs`	Yes
`limitations`	Yes
`source_freshness`	Yes	Feed age band, not the age of every covered rung.
`illustrative_only`	Yes
`equal_target_percentage`	Yes
`hypothetical_amount_usd`	Yes
`maturity_spacing_months`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 18, 2026
- removedOutput schema / properties / rungs / items / properties / option / properties / term_months / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / rungs / items / properties / option / properties / term_months / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changed2 schema fields changedOct 4, 2026

changedOutput schema / properties / rungs / items / properties / option / 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 / rungs / items / properties / option / 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 covered rung has its own record date and age."

addedOutput schema / properties / rungs / items / properties / option / properties / as_of

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

addedOutput schema / properties / rungs / items / properties / option / 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 / rungs / items / properties / option / 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 covered rung."

First observedOct 1, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations are present but thin (readOnlyHint=false, openWorldHint=true, idempotent=false, destructive=false), so the description adds real value: it specifies that each covered rung carries a canonical brinkeradvisor_url plus original source_name/source_url, that uncovered rungs are returned explicitly, and that the tool never touches accounts or trades. It does not mention latency, rate limits, or data freshness for 'current' options. No contradiction with the annotations.

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?

Four sentences, front-loaded with the core action and scope, with the return-shape detail and disclaimers following. Little waste, though the URL/source sentence duplicates information the output schema already conveys.

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 five-parameter tool with an output schema, the description conveys the input semantics, the coverage guarantee of the result, and the ethical/scope boundaries. The remaining gaps are the unexplained optional hypothetical_amount_usd and absent units, which the schema enforces but does not explain.

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. It does cover rung count, term range, and the four instrument types in prose, which maps to four of five parameters, but it never mentions hypothetical_amount_usd (the only optional field) and gives no units or bounds (months, USD limits) beyond what the schema enforces.

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?

Specific verb (build) plus a precisely scoped resource (an educational, equal-weight maturity ladder from current eligible public CD/money-market/Treasury/municipal options). An agent can distinguish it from a rate-comparison or search tool. It stops short of naming any sibling or stating what it is not relative to compare_rates/fetch, so it lands at 4 rather than 5.

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 inputs ('for a requested rung count and term range') and by the negative scope disclaimers (no account access, no trading, no advice), which help route away from trading/advisory tools. However there is no explicit when-to-use trigger and no named alternative, so the agent must infer the conditions.

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?