Skip to main content
Glama

Get global markets overview

get_global_markets_overview
Read-only

Bullrun's Global Markets dashboard in one call: world equity indices (S&P 500, Nasdaq-100, MSCI World, DAX, FTSE 100, Nikkei, Hang Seng, Nifty...), central-bank policy rates and next rate decisions (Fed, ECB, BoE, BoJ, SNB, BoC), 16 sovereign 10-year yields, 20 FX pairs, oil/gas/gold/copper, headline macro tiles (global GDP growth, inflation, debt/GDP, VIX, the broad dollar index, 2s10s curve, US jobless claims), the upcoming economic calendar, market news and the US housing balance. Each row carries a historyCode for get_macro_history. Use for "how are markets doing today", "what's the macro backdrop", "where are rates/yields", "what's on the calendar this week" or a morning briefing. Daily closes, with live intraday index levels while markets are open. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
sectionsNoSections to return. headline = global GDP/inflation/debt, oil, gold, the broad dollar index, US 10Y, 2s10s curve, VIX, EUR/USD, Bitcoin, policy-rate average, OECD unemployment, US jobless claims; indices = 19 world equity indices (live intraday level when a market is open); rates = six major central-bank policy rates + upcoming rate decisions; yields = 16 sovereign 10Y yields; currencies = 20 FX pairs; commodities = Brent, WTI, natural gas, gold, copper; calendar = upcoming high-impact economic releases; news = market headlines; us_housing = US housing-market balance (months' supply, inventory, price cuts). Default: everything except news and us_housing.
newsLimitNoHeadlines to return when the news section is requested.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sections / description
      Previous value: -"Sections to return. headline = global GDP/inflation/debt, oil, gold, DXY, US 10Y, 2s10s curve, VIX, EUR/USD, Bitcoin, policy-rate average, OECD unemployment, US jobless claims; indices = 19 world equity indices (live intraday level when a market is open); rates = six major central-bank policy rates + upcoming rate decisions; yields = 16 sovereign 10Y yields; currencies = 20 FX pairs; commodities = Brent, WTI, natural gas, gold, copper; calendar = upcoming high-impact economic releases; news = market headlines; us_housing = US housing-market balance (months' supply, inventory, price cuts). Default: everything except news and us_housing."New value: +"Sections to return. headline = global GDP/inflation/debt, oil, gold, the broad dollar index, US 10Y, 2s10s curve, VIX, EUR/USD, Bitcoin, policy-rate average, OECD unemployment, US jobless claims; indices = 19 world equity indices (live intraday level when a market is open); rates = six major central-bank policy rates + upcoming rate decisions; yields = 16 sovereign 10Y yields; currencies = 20 FX pairs; commodities = Brent, WTI, natural gas, gold, copper; calendar = upcoming high-impact economic releases; news = market headlines; us_housing = US housing-market balance (months' supply, inventory, price cuts). Default: everything except news and us_housing."
  2. Added

TDQS

A4.1/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=false, so safety is covered. The description adds genuinely new behavioral context beyond them: 'Daily closes, with live intraday index levels while markets are open' tells the agent about data freshness and intraday variability, and 'in one call' signals a bulk single-request payload.

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 purpose and use cases are front-loaded, which is good, but the long parenthetical inventory of indices, central banks and macro tiles substantially duplicates the sections parameter description in the schema. The parenthetical lists (S&P 500, Nasdaq-100, MSCI World, DAX...) could be trimmed without losing selection-relevant information.

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 read-only, zero-required-parameter overview tool, the description covers everything an agent needs: what is returned section by section, freshness of the data, a pointer to get_macro_history for time series, and the triggering question types. No output schema exists, and the description compensates by describing return content in detail.

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 the sections enum is already explained in detail in the schema, including the default of everything except news and us_housing. The description largely repeats that section inventory rather than adding new parameter meaning; its only incremental value is the cross-tool hint about historyCode on each row, which concerns output rather than input.

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?

The description names a specific verb and resource ('Bullrun's Global Markets dashboard in one call') and then enumerates the exact contents: world equity indices, policy rates, 16 sovereign 10Y yields, 20 FX pairs, commodities, macro tiles, calendar and news. It also differentiates itself from get_macro_history by explaining that each row carries a historyCode for that tool.

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?

It gives concrete triggering queries ('how are markets doing today', 'what's the macro backdrop', 'where are rates/yields', 'what's on the calendar this week', morning briefing) and routes history lookups to get_macro_history. It does not explicitly state when to prefer narrower siblings like get_macro_indicators or get_country_macro, so the routing is clear but not exhaustive.

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.