Skip to main content
Glama

AIsa Equities

by one.aisa
OverviewDiscussionsAdmin

Get Latest Interest Rates

get_financial_macro_interest_rates_snapshot
Read-onlyIdempotent

The newest published policy rate of every central bank we cover, one row per bank with the date it is in effect. Pass bank to get one bank only.

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

Input Schema

NameRequiredDescriptionDefault
bankNoOptional central bank code (e.g., FED, ECB, BOJ) to return one bank only. Use the /macro/interest-rates/banks endpoint to get a list of available banks.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / bank / description
      Previous value: -"Optional central bank code (e.g., FED, ECB, BOJ). AIsa also accepts this endpoint without `bank` and returns the latest snapshot for all major central 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: +"Optional central bank code (e.g., FED, ECB, BOJ) to return one bank only. Use the /macro/interest-rates/banks endpoint to get a list of available banks."
    • removedInput schema / properties / bank / enum
      Removed value: -[
-  "FED",
-  "ECB",
-  "BOJ",
-  "BOE",
-  "BOC",
-  "RBA",
-  "PBOC",
-  "SNB",
-  "RBI",
-  "BOK"
-]
  2. Changed2 schema fields changed
    • changedInput schema / properties / bank / description
      Previous value: -"Optional central bank code (e.g., FED, ECB, BOJ) to return one bank only. Use the /macro/interest-rates/banks endpoint to get a list of available banks."New value: +"Optional central bank code (e.g., FED, ECB, BOJ). AIsa also accepts this endpoint without `bank` and returns the latest snapshot for all major central 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"
+]
  3. Changed2 schema fields changed
    • changedInput schema / properties / bank / description
      Previous value: -"Optional central bank code (e.g., FED, ECB, BOJ). AIsa also accepts this endpoint without `bank` and returns the latest snapshot for all major central 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: +"Optional central bank code (e.g., FED, ECB, BOJ) to return one bank only. Use the /macro/interest-rates/banks endpoint to get a list of available banks."
    • removedInput schema / properties / bank / enum
      Removed value: -[
-  "FED",
-  "ECB",
-  "BOJ",
-  "BOE",
-  "BOC",
-  "RBA",
-  "PBOC",
-  "SNB",
-  "RBI",
-  "BOK"
-]
  4. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so the safety profile is covered. The description adds the row-level return shape and a pricing disclosure ($0.02 per successful request), but the return shape is largely redundant with the existing output schema, leaving the pricing note as the only substantive addition.

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 tight sentences with the core scope front-loaded ahead of the filter note. The injected pricing blockquote adds boilerplate length, but the substantive prose is efficient.

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 an output schema present, return values need no explanation, and annotations carry the safety profile. The description covers resource, scope, and filter adequately; only the sibling-differentiation against the historical rates tool is left implicit.

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 bank parameter is fully documented in the schema, including example codes and a pointer to the banks endpoint. The description only restates the optional single-bank behavior, adding no syntax or format detail 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 gives a specific resource (central bank policy rates) with an explicit scope qualifier: 'newest published' and 'one row per bank with the date it is in effect.' This implicitly separates it from the time-series sibling get_financial_macro_interest_rates, though it never names that sibling explicitly, so it stops short of a 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?

It states the filter behavior ('Pass bank to get one bank only'), which is clear usage for the optional parameter. However, it never says when to prefer this snapshot over the historical get_financial_macro_interest_rates tool, leaving the key routing decision to inference.

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

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