Skip to main content
Glama

get_global_equity_benchmark

Read-only

Global equity index benchmarks — S&P 500, Nasdaq, Russell 2000, Stoxx 600, DAX, FTSE 100, Nikkei 225, Hang Seng, Shanghai Composite, MSCI EM. YTD returns, P/E ratios, and risk-on/risk-off global signal. Live source. Returns HTTP 503 (no charge) if upstream source unavailable for >50% of fields. | x402 SLA: $0.10 USDC per call. Returns HTTP 503 (no charge) when upstream data sources unavailable. data_source field discloses provenance (fred_api/fred_csv/fred_mixed).

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

Input Schema

NameRequiredDescriptionDefault
regionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description goes meaningfully beyond that by disclosing failure behavior (HTTP 503 with no charge when upstream sources are unavailable for >50% of fields), per-call pricing ($0.10 USDC via x402), and a data_source provenance field (fred_api/fred_csv/fred_mixed) — all operationally useful to an agent. It falls short of 5 because it never describes the response shape or what the risk-on/risk-off signal looks like.

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

Conciseness3/5

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

The index/metric enumeration is front-loaded and valuable, but the sentence 'Returns HTTP 503 (no charge) if upstream source unavailable for >50% of fields' is near-duplicated later as 'Returns HTTP 503 (no charge) when upstream data sources unavailable' — one of them is pure waste. 'Live source' is also a vague fragment that adds little absent a definition of freshness.

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?

For a single-optional-parameter read tool with no output schema, the description covers coverage universe, metrics, pricing, provenance, and failure semantics — enough for an agent to call it safely. The remaining gap is how the region parameter scopes results and what a default call returns, which the description never addresses.

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 0%, so the enum values (us/europe/asia/emerging/all) carry all the meaning themselves. The description indirectly helps by grouping the listed indices by region, letting an agent map 'europe' to Stoxx/DAX/FTSE and 'emerging' to MSCI EM, but it never mentions the region parameter, its default, or what 'all' returns. Useful implicit mapping, but the gap is real.

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?

The description names a specific resource (global equity index benchmarks) and enumerates the covered indices — S&P 500, Nasdaq, Russell 2000, Stoxx 600, DAX, FTSE 100, Nikkei 225, Hang Seng, Shanghai Composite, MSCI EM — plus the metrics returned (YTD returns, P/E ratios, risk-on/risk-off signal). An agent can tell what data it gets. It does not explicitly differentiate itself from the many sibling benchmark tools (e.g., get_fx_rate_benchmark, get_credit_spread_benchmark), leaving scope boundaries inferred.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no alternative tool is named. The only usage-adjacent content is the region enum and the note that the source is live, which implies 'use this for current global equity index data' but never states it. The agent must infer fit from the index list alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources