FinChiefs

Get central bank and policy-maker signals

get_policy_signals

Read-only

Structured reads of central-bank and multilateral publications: decisions, stance (-2 dovish to +2 hawkish), guidance, conditions, speaker and forecasts, each with a link to the original. Newest first; pages via offset / next_offset.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_policy_signals"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Items per page, at most 100. Default 40.
`since`	No	Start date YYYY-MM-DD. Default: 30 days ago. The free plan reaches back 7 days for individual items.
`until`	No	End date YYYY-MM-DD, inclusive. Default: today.
`offset`	No	Skip this many items; pass the previous response's next_offset to read the next page.
`doc_type`	No
`provider_id`	No	A central bank or multilateral (id from list_providers). Matches the publisher or the institution whose view it is.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuinely new context — deterministic newest-first ordering, offset/next_offset paging, and the -2..+2 dovish/hawkish encoding of stance. It stops short of describing edge cases (empty windows, plan truncation) that the schema mentions only for `since`.

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 compact clauses, front-loaded with what is returned followed by ordering/paging, with no filler. Slightly dense in packing stance, speaker, conditions and forecasts into one list, but nothing is wasted.

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 no output schema, the description usefully enumerates the returned fields and the stance scale, and it covers pagination — the two things an agent most needs. It is thin on filter semantics (doc_type, provider_id) and on plan-based date truncation, which are the remaining gaps.

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 83%, so most parameters are already documented, and the description only restates the paging mechanism (offset/next_offset). It adds nothing about doc_type values (the one enum, undocumented in the schema) or provider_id semantics, leaving a real gap untouched.

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?

States a specific verb+resource ('structured reads of central-bank and multilateral publications') and enumerates the content returned (decisions, stance, guidance, forecasts, links). An agent can see it's a curated feed of policy documents, though it never names the search_* siblings or explains how it differs from them.

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 only implied: 'newest first; pages via offset / next_offset' tells the agent how to iterate, but not when to pick this over search_macro_views or summarize_views, nor any exclusions. Prerequisites and the free-plan 7-day limit appear only in the schema, not as routing guidance.

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

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