Skip to main content
Glama
Sign In

Statistics of the World

by com.statisticsoftheworld
OverviewDiscussionsAdmin

get_market_quotes

Read-onlyIdempotent

Market quotes: delayed quotes collected from Yahoo Finance (32 stock market index levels, US index futures, front-month commodity futures, US dollar exchange rates), each with its market time (asOf, UTC) and change on the previous session close; and official daily settlement prices of Chinese commodity futures (most-traded contract) read from the Shanghai and Zhengzhou exchanges, with trade date and change on the previous settlement. Every quote names its source, unit and source URL. Official daily reference rates (ECB, central banks, treasuries) are separate: use get_series_data.

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

Input Schema

NameRequiredDescriptionDefault
idsNoExact quote IDs, for example YF.IDX.USA (S&P 500), YF.IDX.JPN (Nikkei 225), YF.BRENT or YF.FX.EUR. Narrows the group.
groupNoindices: stock index levels; futures: US index futures; commodities: front-month commodity futures; china: official Chinese futures settlements; crypto: top 250 crypto assets in US dollars (CoinGecko); fx: US dollar exchange rates; all (default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / group / description
      Previous value: -"indices: stock index levels; futures: US index futures; commodities: front-month commodity futures; china: official Chinese futures settlements; fx: US dollar exchange rates; all (default)."New value: +"indices: stock index levels; futures: US index futures; commodities: front-month commodity futures; china: official Chinese futures settlements; crypto: top 250 crypto assets in US dollars (CoinGecko); fx: US dollar exchange rates; all (default)."
    • changedInput schema / properties / group / enum
      Previous value: -[
-  "indices",
-  "futures",
-  "commodities",
-  "china",
-  "fx",
-  "all"
-]New value: +[
+  "indices",
+  "futures",
+  "commodities",
+  "china",
+  "crypto",
+  "fx",
+  "all"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / group / description
      Previous value: -"indices: stock index levels; futures: US index futures; commodities: front-month commodity futures; fx: US dollar exchange rates; all (default)."New value: +"indices: stock index levels; futures: US index futures; commodities: front-month commodity futures; china: official Chinese futures settlements; fx: US dollar exchange rates; all (default)."
    • changedInput schema / properties / group / enum
      Previous value: -[
-  "indices",
-  "futures",
-  "commodities",
-  "fx",
-  "all"
-]New value: +[
+  "indices",
+  "futures",
+  "commodities",
+  "china",
+  "fx",
+  "all"
+]
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description's job is to add what they cannot. It does: quotes are DELAYED rather than live, sourced from Yahoo Finance and named Chinese exchanges, each carries asOf in UTC, unit and source URL, and 'change' is measured against the previous session close or prior settlement.

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?

Front-loaded with the resource and a useful enumeration, but the definition is one long sentence dense with parentheticals covering two distinct data families. The routing sentence at the end is well-placed, though the whole is longer than two optional parameters warrant.

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 two-optional-parameter read tool with no output schema, it covers provenance, freshness (delayed), units, and the asOf/change comparison semantics an agent needs to call it correctly. Return shape and any pagination beyond the ids maxItems cap are unstated, a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, yet the description still clarifies the interaction of the two parameters, framing ids as narrowing whichever group is used and reinforcing group meanings. The enum descriptions in the schema do the heavy lifting and the description is consistent with them.

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 ('Market quotes') and enumerates exactly what is returned: delayed Yahoo Finance quotes covering 32 index levels, US index futures, front-month commodity futures and USD FX rates, plus official Chinese commodity futures settlements. Distinguishable at a glance from get_market_history and get_onchain_quotes.

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?

Explicitly excludes one genuine alternative: official daily reference rates (ECB, central banks, treasuries) are routed to get_series_data. It does not address when to prefer get_market_history or get_onchain_quotes, but the most likely confusion is resolved.

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

All Statistics of the World 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