FilingDelta

Free sample central-bank card

sample_policy

Read-onlyIdempotent

Free sample rate-decision card for any covered central bank, no payment: the bank's PREVIOUS meeting as a full card, same schema as get_policy (decision, rate, change, vote, dissent, source link), with access "full", sample_of "previous_meeting" and a disclaimer. A latest object gives the current meeting only as {meeting_date, access "paid", content_hash, buy_with}; the current decision itself is in the paid get_policy card. Policy ids: BOE, FED, ECB, BOJ, RBA, BOC, SNB, NOR, SWE, MEX, BOK, TUR, IND, ZAF, CHN, IDN, ETH, RUS, EGY, IRN, BCB, NZL.

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.4/5.0

Behavior5/5

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

Annotations already establish a safe read-only operation, and the description adds substantial context beyond them: access='full', sample_of='previous_meeting', a disclaimer, the same schema as get_policy, and a latest object containing only paid metadata and a buy_with pointer. This is exactly the kind of behavioral detail an agent needs.

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 description is dense and front-loads the free-sample purpose and return shape. It is somewhat long and redundantly repeats the full id enum already present in the schema, but the remaining sentences earn their place by explaining the return structure and paid boundary.

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?

With an output schema present and annotations covering safety, the description still supplies the critical missing context: what the free sample contains, how it differs from the paid current card, and what the latest object exposes. Nothing needed to call it correctly is missing.

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 coverage is 100% and the single parameter has a full enum with description. The description repeats the policy id list but adds no syntax or format detail beyond what the schema already provides, so baseline 3 is appropriate.

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 states a specific resource and scope: a free sample rate-decision card covering a central bank's PREVIOUS meeting, with full card fields. It explicitly distinguishes this from the paid get_policy card that contains the current decision.

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?

It clearly says this tool provides the previous meeting for free and that the current decision is in the paid get_policy card, which gives the agent a practical alternative. It stops short of an explicit 'use this when...' sentence, but the routing is clear.

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?