Skip to main content
Glama
Sign In

FinChiefs

by com.finchiefs
OverviewDiscussionsAdmin

Get upcoming central bank meetings and the research tally

get_central_bank_meetings
Read-only

Each central bank's next rate decision (and decisions of the past week): date, FinChiefs' preview, the research tally (one hike/hold/cut vote per research house — banks, asset managers, independent research firms and podcasts — counted from published notes) with its mix by house type, and the outcome once decided. Pass banks to also list each house with its call and latest note. Covers the G10 banks and India.

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_central_bank_meetings"
  }
}

Input Schema

NameRequiredDescriptionDefault
banksNoCentral banks by code or short name: fed, ecb, boe, boj, boc, rba, snb, pboc (meetings also cover Riksbank, Norges Bank, RBNZ, RBI). Omit for all.
housesNoList each research house's call and note (default: true when banks are given, false otherwise).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / houses / description
      Previous value: -"List each research house's call and note (default true)."New value: +"List each research house's call and note (default: true when banks are given, false otherwise)."
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful scope context — G10 plus India coverage, inclusion of the past week's decisions, and that the tally is counted from published notes across banks, asset managers, independent researchers and podcasts — but says nothing about staleness, update cadence, or behavior with invalid bank codes.

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?

Front-loaded with the resource and its payload, and only two sentences. The first sentence is long and heavily parenthetical, which slows parsing slightly, but each clause carries real information about what is returned.

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 does the work of describing return fields (date, preview, tally, mix, outcome) and coverage. Minor gaps remain: the exact forward window for 'next rate decision' and how many meetings are returned are unspecified.

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%, so baseline is 3; the description earns a bit more by explaining the functional consequence of `banks` (it also expands each house's call and latest note) rather than just restating the parameter. It does not add format details (code vs short name) beyond what the schema already documents.

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?

Names a specific resource (central bank rate decisions, upcoming plus the past week) and enumerates the returned content: date, FinChiefs preview, research tally with mix by house type, and outcome. It also states coverage (G10 plus India), so it is clearly distinguishable from rate-level siblings like get_policy_rates.

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 implied by the content description (a forward-looking decision calendar), and it gives the conditional 'Pass banks to also list each house with its call', plus 'Omit for all'. But it never says when to prefer get_policy_rates or get_policy_signals instead, nor any exclusions.

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

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