EL7.AI

Central bank members and hawk/dove scores

el7_people_cb_members

Read-onlyIdempotent

Active policy-setting members of each central bank (or one) with role, voter status, hawk/dove score (null = no recent scored speech, not neutral; the text states how many are scored), speech count and latest speech, plus each bank's average over the scored. Use for 'who is the most hawkish on the FOMC' or 'who votes this year'. Then el7_person for one member.

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": "el7_people_cb_members"
  }
}

Input Schema

Name	Required	Description	Default
`bank`	No	One bank (fed, ecb, boe, boj, boc, rba, rbnz, snb). Omit for every bank.
`lang`	No	Output language: 'en' (default) or 'ar' for EL7's stored Arabic text.

Output Schema

Name	Required	Description	Default
`as_of`	No	Source freshness: the newest source timestamp behind this result, or null when none is verified. Never request time.
`banks`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely non-obvious behavior: null hawk/dove means no recent scored speech rather than neutral, per-bank averages are computed only over the scored, and the payload states how many members are scored. Return shape itself is left to the output schema.

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 sentences, front-loaded with the resource and the returned fields, followed by usage examples and the drill-down hint. The parenthetical field list is dense but every element earns its place; only minor tightening is possible.

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?

For a two-optional-parameter, read-only list tool with an output schema and full annotation coverage, this covers purpose, returned content, null semantics, aggregation scope and the follow-up call. Nothing needed to invoke 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 description coverage is 100% and both parameters are fully enumerated, so the schema carries the detail. The description only reinforces the optional single-bank scoping ('or one') and adds no format or behavior notes for 'lang'. Baseline 3 applies.

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?

States a specific verb+resource: active policy-setting members of a central bank (one or all), returned with role, voter status, hawk/dove score, speech count and latest speech. This is clearly distinct from sibling member-level tools like el7_person, which the description names as the drill-down alternative.

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?

Gives concrete when-to-use phrasings ('who is the most hawkish on the FOMC', 'who votes this year') and routes to el7_person for a single member. It does not address nearby alternatives such as el7_cb_tone_ranking or el7_people_search, so the routing picture is not complete.

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

All EL7.AI 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?