FilingDelta

Central-bank decision card (paid $0.02)

get_policy

Read-onlyIdempotent

Paid $0.02 USDC on Base. Call when you need the latest central-bank rate decision (hike, hold or cut) for a major or emerging-market bank: policy rate, change in bps, vote, next meeting and official source. Free: sample_policy. Policy ids: BOE, FED, ECB, BOJ, RBA, BOC, SNB, NOR, SWE, MEX, BOK, TUR, IND, ZAF, CHN, IDN, ETH, RUS, EGY, IRN, BCB, NZL. Others return 404 (no charge).

Input Schema

Name	Required	Description	Default
`id`	Yes	Central bank id

Output Schema

Name	Required	Description	Default
`id`	Yes
`summary`	No
`decision`	No
`bank_rate`	No
`card_type`	No
`change_bps`	No
`source_url`	Yes
`institution`	Yes
`generated_at`	No
`previous_bank_rate`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 2, 2026

changedInput schema / properties / id / enum

Previous value: -[
-  "BOE",
-  "FED",
-  "ECB",
-  "BOJ",
-  "RBA",
-  "BOC",
-  "SNB",
-  "NOR",
-  "SWE",
-  "MEX",
-  "BOK",
-  "TUR",
-  "IND",
-  "ZAF",
-  "CHN",
-  "IDN",
-  "ETH",
-  "RUS",
-  "EGY",
-  "IRN",
-  "BCB"
-]New value: +[
+  "BOE",
+  "FED",
+  "ECB",
+  "BOJ",
+  "RBA",
+  "BOC",
+  "SNB",
+  "NOR",
+  "SWE",
+  "MEX",
+  "BOK",
+  "TUR",
+  "IND",
+  "ZAF",
+  "CHN",
+  "IDN",
+  "ETH",
+  "RUS",
+  "EGY",
+  "IRN",
+  "BCB",
+  "NZL"
+]

changedOutput schema / properties / bank_rate / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

changedOutput schema / properties / change_bps / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

changedOutput schema / properties / decision / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / previous_bank_rate / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

changedOutput schema / required

Previous value: -[
-  "id",
-  "institution",
-  "decision",
-  "source_url"
-]New value: +[
+  "id",
+  "institution",
+  "source_url"
+]

Changed1 schema field changedOct 23, 2026

changedInput schema / properties / id / enum

Previous value: -[
-  "BOE",
-  "FED",
-  "ECB",
-  "BOJ",
-  "RBA",
-  "BOC",
-  "SNB",
-  "NOR",
-  "SWE",
-  "MEX",
-  "BOK",
-  "TUR",
-  "BCB"
-]New value: +[
+  "BOE",
+  "FED",
+  "ECB",
+  "BOJ",
+  "RBA",
+  "BOC",
+  "SNB",
+  "NOR",
+  "SWE",
+  "MEX",
+  "BOK",
+  "TUR",
+  "IND",
+  "ZAF",
+  "CHN",
+  "IDN",
+  "ETH",
+  "RUS",
+  "EGY",
+  "IRN",
+  "BCB"
+]

Changed1 schema field changedOct 22, 2026

changedInput schema / properties / id / enum

Previous value: -[
-  "BOE",
-  "FED",
-  "ECB",
-  "BOJ",
-  "RBA",
-  "BOC",
-  "SNB",
-  "NOR",
-  "SWE",
-  "MEX",
-  "BOK",
-  "BCB"
-]New value: +[
+  "BOE",
+  "FED",
+  "ECB",
+  "BOJ",
+  "RBA",
+  "BOC",
+  "SNB",
+  "NOR",
+  "SWE",
+  "MEX",
+  "BOK",
+  "TUR",
+  "BCB"
+]

Changed1 schema field changedOct 22, 2026

changedInput schema / properties / id / enum

Previous value: -[
-  "BOE",
-  "FED",
-  "ECB",
-  "BOJ",
-  "RBA",
-  "BOC",
-  "SNB",
-  "NOR",
-  "SWE",
-  "MEX",
-  "BCB"
-]New value: +[
+  "BOE",
+  "FED",
+  "ECB",
+  "BOJ",
+  "RBA",
+  "BOC",
+  "SNB",
+  "NOR",
+  "SWE",
+  "MEX",
+  "BOK",
+  "BCB"
+]

Changed1 schema field changedOct 21, 2026

changedInput schema / properties / id / enum

Previous value: -[
-  "BOE",
-  "FED",
-  "ECB",
-  "BOJ",
-  "RBA",
-  "BOC",
-  "SNB",
-  "NOR",
-  "SWE"
-]New value: +[
+  "BOE",
+  "FED",
+  "ECB",
+  "BOJ",
+  "RBA",
+  "BOC",
+  "SNB",
+  "NOR",
+  "SWE",
+  "MEX",
+  "BCB"
+]

Changed1 schema field changedOct 17, 2026

changedInput schema / properties / id / enum

Previous value: -[
-  "BOE",
-  "FED",
-  "ECB",
-  "BOJ",
-  "RBA",
-  "BOC",
-  "SNB"
-]New value: +[
+  "BOE",
+  "FED",
+  "ECB",
+  "BOJ",
+  "RBA",
+  "BOC",
+  "SNB",
+  "NOR",
+  "SWE"
+]

Changed3 schema fields changedOct 14, 2026

addedInput schema / properties / id / description
```
Added value: +"Central bank id"
```

addedInput schema / properties / id / enum

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "bank_rate": {
+      "type": "number"
+    },
+    "card_type": {
+      "type": "string"
+    },
+    "change_bps": {
+      "type": "number"
+    },
+    "decision": {
+      "type": "string"
+    },
+    "generated_at": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "institution": {
+      "type": "string"
+    },
+    "previous_bank_rate": {
+      "type": "number"
+    },
+    "source_url": {
+      "type": "string"
+    },
+    "summary": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "institution",
+    "decision",
+    "source_url"
+  ],
+  "type": "object"
+}

First observedOct 13, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover read-only, idempotent and non-destructive semantics, and the description adds what they cannot: a fixed $0.02 USDC-on-Base cost, the free sibling, and that unsupported ids fail with 404 at no charge. That pricing and failure-billing behavior is exactly the context an agent needs before spending money.

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?

Cost, trigger and return fields are front-loaded in one tight sentence, followed by the free alternative. The long enumeration of all 22 policy ids duplicates the schema enum verbatim and consumes space without adding information.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Price, coverage set, failure mode, free alternative and returned fields are all present, and an output schema exists so return structure needn't be re-explained. Nothing material is missing for an agent to decide and call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with a full 22-value enum, so the parameter is already well documented; repeating the ids in prose is largely redundant. The added value is the semantics of out-of-enum input — others return 404 and are not charged — which the schema cannot express.

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 names a specific verb and resource — the latest central-bank rate decision — and enumerates exactly what is returned: policy rate, change in bps, vote, next meeting, official source. Sibling names like sample_policy, get_macro and get_cpi are implicitly differentiated by the central-bank-decision scope.

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

Usage Guidelines5/5

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

It states the trigger explicitly ("Call when you need the latest central-bank rate decision") and routes the agent to a free alternative ("Free: sample_policy"). The note that unsupported ids return 404 with no charge also tells the agent what happens if it strays outside the covered set.

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

All FilingDelta 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?