EL7.AI

Central bank hawk/dove ranking

el7_cb_tone_ranking

Read-onlyIdempotent

Ranks all eight central banks from most hawkish to most dovish by the tone score of their latest decision statement, with the previous score and the change. Use to compare policy stance across banks. Not for one bank's detail — use el7_cb_overview or el7_cb_statement_diff.

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

Input Schema

Name	Required	Description	Default
`lang`	No	Output language: 'en' (default) or 'ar' for EL7's stored Arabic text.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds behavior beyond that: the ranking covers the full set of eight banks, is based on the latest decision statement only, and returns previous score plus change. It doesn't mention update cadence or how ties are broken, which keeps it off a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, each doing a distinct job: what it returns, when to use it, when not to and what to use instead. No filler and the alternative routing is placed at the end where it reads as a natural redirect.

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?

Output schema exists, so return values needn't be spelled out, and the description still sketches them. Scope, use case, and alternatives are all covered; the only gap is that 'tone score' and its scale are never characterized, which matters if an agent needs to interpret magnitudes.

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?

Only one parameter (lang) and schema coverage is 100%, with the enum documented in the schema itself, so the baseline is 3. The description adds nothing about language handling or what 'ar' returns, but it doesn't need to given the schema does that work.

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 and resource ('ranks all eight central banks ... by the tone score of their latest decision statement') and pins the scope to all eight banks and the latest statement. It also names what the output contains (previous score and the change), so an agent knows exactly what this tool produces versus el7_cb_statement_diff.

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?

Explicitly states the use case ('compare policy stance across banks') and the exclusion with named alternatives ('Not for one bank's detail — use el7_cb_overview or el7_cb_statement_diff'). This is the when/when-not/alternative pattern at full strength.

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?