Skip to main content
Glama

TipRanks

by com.tipranks
OverviewDiscussions(1)Admin

get_index_quote

Read-onlyIdempotent

Returns the real-time quote for a major market index.

Index symbols: ^GSPC (S&P 500), ^NDX (Nasdaq 100), ^IXIC (Nasdaq
Composite), ^DJI (Dow Jones), ^RUT (Russell 2000), ^GSPTSE (TSX),
^FTSE (FTSE 100), ^GDAXI (DAX 40), ^FCHI (CAC 40), ^STOXX50E
(Euro STOXX 50), ^IBEX (IBEX 35), ^N225 (Nikkei), ^AXJO (ASX 200),
^AORD (All Ords), ^HSI (Hang Seng), ^STI (STI), ^BSESN (Sensex),
^VIX (VIX).

Broker / CFD names map to the index they track (the same map the AI
chat uses): 'US Tech 100' / 'NAS100' / 'USTEC' -> ^NDX; 'US 500' /
'SPX500' -> ^GSPC; 'Wall Street 30' / 'US 30' -> ^DJI; 'US 2000' /
'US Small Cap 2000' -> ^RUT; 'Germany 40' / 'GER40' -> ^GDAXI;
'UK 100' -> ^FTSE; 'France 40' -> ^FCHI; 'Euro 50' / 'EU50' ->
^STOXX50E; 'Spain 35' -> ^IBEX; 'Japan 225' -> ^N225; 'Australia 200'
-> ^AXJO; 'Hong Kong 50' -> ^HSI. 'Nasdaq Composite' is
^IXIC; 'Nasdaq 100' and the Nasdaq 100 CFD names above are ^NDX —
different indices at different levels, so quote the one the user named
and name it. A bare 'Nasdaq' is ambiguous: say which one you quote. For
an index not listed here (e.g. 'S&P 100'), call it by its own symbol —
a listed index with a similar name is a different index.

yearHigh / yearLow are the feed's trailing-year range, roughly the past
12-13 months: call them trailing-year figures. For a year-to-date or
calendar-year change, a dated extreme or an exact 52-week figure use
get_index_historical, since the quote does not date its extremes.

Args:
    symbol: Index symbol (e.g. '^GSPC' for S&P 500)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesIndex symbol, e.g. '^GSPC' for the S&P 500.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_index_quoteOutput",
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, open-world behavior, so the safety profile is covered. The description adds real behavioral context no structured field carries: yearHigh/yearLow are a trailing ~12-13 month feed range with undated extremes, which changes how the agent should present the data. It stops short of describing the full return shape or freshness/latency of 'real-time'.

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?

Long, but the bulk is content-bearing symbol mapping rather than filler, and the core statement plus the historical-tool handoff are front-loaded. The alias list is dense and could be trimmed of redundancy, but nothing reads as padding.

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?

With no output schema, the description correctly compensates by explaining the semantics of the returned range fields and directing ambiguous-name cases. Together with the annotation coverage, an agent has everything needed to select and invoke it correctly.

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

Parameters4/5

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

Schema coverage is 100% and there is only one parameter, so the baseline would be 3. However the description goes well beyond the schema's 'e.g. ^GSPC' stub by supplying a broker/CFD alias map ('US Tech 100'/'NAS100' -> ^NDX, etc.) that lets the agent resolve natural-language index names, plus a warning about near-name collisions.

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?

Opens with a specific verb+resource: 'Returns the real-time quote for a major market index.' The scope is unambiguous and an agent can separate it from get_index_historical, get_market_performance, and other quote tools from the first sentence alone.

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 routes the agent away from this tool when the need is YTD/calendar-year changes, dated extremes, or exact 52-week figures ('use get_index_historical'). It also gives concrete disambiguation rules for ambiguous inputs (bare 'Nasdaq', 'S&P 100') and the policy of quoting the index the user named.

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

All TipRanks 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