AIsa Equities

Get Historical Interest Rates

get_financial_macro_interest_rates

Read-onlyIdempotent

The daily policy rate of one central bank: one row per calendar day, newest first, 10 rows per page. A rate change appears on the first day the new rate is in effect. For the Federal Reserve the rate is the midpoint of the target range.

Published reference price: $0.02 USD per successful request. Account-specific pricing and final settlement may differ.

Input Schema

Name	Required	Description
`bank`	Yes	The central bank code, e.g. FED, ECB, BOJ. Use the /macro/interest-rates/banks endpoint to get the list of available banks.
`cursor`	No	Opaque pagination cursor from a previous response's next_page_url. When provided, all other query parameters are ignored: the cursor carries the original request's filters. Treat it as opaque; do not construct or modify it.
`end_date`	No	The last date to return, inclusive, in YYYY-MM-DD format. Defaults to today.
`start_date`	No	The first date to return, inclusive, in YYYY-MM-DD format. Defaults to five years before end_date when both dates are omitted; omit it with an end_date to get all available history through that date.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 15, 2026

changedInput schema / properties / bank / description

Previous value: -"The bank whose interest rates to return. Use the /macro/interest-rates/banks endpoint to get a list of available banks. Case-sensitive: must be uppercase. A lowercase code returns HTTP 404 \"No data found\", which reads like an empty result rather than a bad argument."New value: +"The central bank code, e.g. FED, ECB, BOJ. Use the /macro/interest-rates/banks endpoint to get the list of available banks."

removedInput schema / properties / bank / enum

Removed value: -[
-  "FED",
-  "ECB",
-  "BOJ",
-  "BOE",
-  "BOC",
-  "RBA",
-  "PBOC",
-  "SNB",
-  "RBI",
-  "BOK"
-]

addedInput schema / properties / cursor

Added value: +{
+  "description": "Opaque pagination cursor from a previous response's next_page_url. When provided, all other query parameters are ignored: the cursor carries the original request's filters. Treat it as opaque; do not construct or modify it.",
+  "type": "string"
+}

changedInput schema / properties / end_date / description

Previous value: -"The end date of the interest rates to return in YYYY-MM-DD format."New value: +"The last date to return, inclusive, in YYYY-MM-DD format. Defaults to today."

changedInput schema / properties / start_date / description

Previous value: -"The start date of the interest rates to return in YYYY-MM-DD format."New value: +"The first date to return, inclusive, in YYYY-MM-DD format. Defaults to five years before end_date when both dates are omitted; omit it with an end_date to get all available history through that date."

Changed5 schema fields changedOct 15, 2026

changedInput schema / properties / bank / description

Previous value: -"The central bank code, e.g. FED, ECB, BOJ. Use the /macro/interest-rates/banks endpoint to get the list of available banks."New value: +"The bank whose interest rates to return. Use the /macro/interest-rates/banks endpoint to get a list of available banks. Case-sensitive: must be uppercase. A lowercase code returns HTTP 404 \"No data found\", which reads like an empty result rather than a bad argument."

addedInput schema / properties / bank / enum

Added value: +[
+  "FED",
+  "ECB",
+  "BOJ",
+  "BOE",
+  "BOC",
+  "RBA",
+  "PBOC",
+  "SNB",
+  "RBI",
+  "BOK"
+]

removedInput schema / properties / cursor

Removed value: -{
-  "description": "Opaque pagination cursor from a previous response's next_page_url. When provided, all other query parameters are ignored: the cursor carries the original request's filters. Treat it as opaque; do not construct or modify it.",
-  "type": "string"
-}

changedInput schema / properties / end_date / description

Previous value: -"The last date to return, inclusive, in YYYY-MM-DD format. Defaults to today."New value: +"The end date of the interest rates to return in YYYY-MM-DD format."

changedInput schema / properties / start_date / description

Previous value: -"The first date to return, inclusive, in YYYY-MM-DD format. Defaults to five years before end_date when both dates are omitted; omit it with an end_date to get all available history through that date."New value: +"The start date of the interest rates to return in YYYY-MM-DD format."

Changed5 schema fields changedOct 15, 2026

changedInput schema / properties / bank / description

Previous value: -"The bank whose interest rates to return. Use the /macro/interest-rates/banks endpoint to get a list of available banks. Case-sensitive: must be uppercase. A lowercase code returns HTTP 404 \"No data found\", which reads like an empty result rather than a bad argument."New value: +"The central bank code, e.g. FED, ECB, BOJ. Use the /macro/interest-rates/banks endpoint to get the list of available banks."

removedInput schema / properties / bank / enum

Removed value: -[
-  "FED",
-  "ECB",
-  "BOJ",
-  "BOE",
-  "BOC",
-  "RBA",
-  "PBOC",
-  "SNB",
-  "RBI",
-  "BOK"
-]

addedInput schema / properties / cursor

Added value: +{
+  "description": "Opaque pagination cursor from a previous response's next_page_url. When provided, all other query parameters are ignored: the cursor carries the original request's filters. Treat it as opaque; do not construct or modify it.",
+  "type": "string"
+}

changedInput schema / properties / end_date / description

Previous value: -"The end date of the interest rates to return in YYYY-MM-DD format."New value: +"The last date to return, inclusive, in YYYY-MM-DD format. Defaults to today."

changedInput schema / properties / start_date / description

Previous value: -"The start date of the interest rates to return in YYYY-MM-DD format."New value: +"The first date to return, inclusive, in YYYY-MM-DD format. Defaults to five years before end_date when both dates are omitted; omit it with an end_date to get all available history through that date."

First observedSep 15, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, open-world, non-destructive query. The description adds valuable behavioral detail beyond annotations: page size (10 rows), ordering (newest first), rate-change timing, and the Federal Reserve midpoint convention. Pricing is also disclosed.

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?

The main content is front-loaded and concise: it describes the returned data shape and pagination first. The pricing notice is boilerplate but clearly separated. No sentence is wasted, though the description is not maximally tight.

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

Completeness3/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 need not be exhaustive, and the description usefully supplements it with row frequency, ordering, and rate-change semantics. However, it omits guidance on when to prefer this tool over the snapshot sibling, leaving a meaningful usage gap for an agent choosing between the two.

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%, so the schema already fully documents `bank`, `cursor`, `start_date`, and `end_date`. The description adds only that data is for one central bank, which is implied by the required `bank` parameter, but does not explain any parameter syntax beyond the schema.

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 clearly identifies the resource: daily policy rates for one central bank, one row per calendar day, newest first. It does not explicitly name the sibling `get_financial_macro_interest_rates_snapshot` as the alternative for current data, but it is clear enough to distinguish from most other tools.

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 explicit when-to-use or when-not-to-use guidance is provided, and the sibling snapshot tool is not mentioned. The description implies a historical daily-rate query but leaves the agent to infer that this tool is for historical rates rather than a current snapshot.

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

All AIsa Equities 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?