QuantGeeks GEX

Price bars

quantgeeks_get_price_bars

Read-onlyIdempotent

Requires a QuantGeeks plan; not available without signing in (the call asks the user to sign in) or with a free account (the call says it needs a plan). Price bars, newest last, at most 100: by default 5-minute bars for the session (today or date), or daily bars when days is more than 1 or interval is D. interval is 1m, 5m, 15m or D; limit (1 to 100) keeps the newest bars; days (up to 250) sets the daily window. The reply gives from, to, returned and available so you can page by date, and latest (the live price, its time and basis, as quantgeeks_get_last_price gives it).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "quantgeeks_get_price_bars"
  }
}

Input Schema

Name	Required	Description
`date`	No	Session date, YYYY-MM-DD (US Eastern). Default: the most recent regular session.
`days`	No	Daily window in days (more than 1 selects daily bars).
`limit`	No	How many of the newest bars (default and maximum 100).
`symbol`	Yes	Ticker, e.g. SPX (maps to its 0DTE option root SPXW), SPY, QQQ, VIX.
`interval`	No	1m, 5m, 15m or D. Default 5m (D when days > 1).

Output Schema

Name	Required	Description	Default
`to`	Yes
`bars`	Yes
`from`	Yes
`note`	No
`as_of`	Yes
`access`	Yes
`latest`	No
`notice`	Yes
`source`	Yes
`symbol`	Yes
`account`	No
`preview`	Yes
`interval`	Yes
`pro_plan`	No
`returned`	Yes
`available`	Yes
`truncated`	No
`truncated_more`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: a paid plan is required and unauthenticated/free calls fail with sign-in prompts, plus how to page using `from`/`to`/`returned`/`available`. That auth and paging context is valuable but is not expanded further (e.g. rate limits, what happens at market close).

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?

Front-loads the access caveat, then the core purpose, then the parameter and return semantics in a logical order with no filler. Sentences are dense and reference-like rather than prose, which suits a tool description but makes them slightly harder to skim.

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 bar-fetch tool with a documented output schema, it covers access requirements, granularity defaults, limits, and how to page — the remaining gaps (exact bar fields) are handled by the output schema.

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%, so the baseline would be 3. The description nevertheless adds cross-parameter meaning the schema only partly conveys — that `days` > 1 or interval=D jointly switch to daily mode, that `limit` retains the newest bars, and that the response window enables date-based paging.

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 ('Price bars, newest last, at most 100') plus the exact defaults and granularity rules. It even differentiates itself from quantgeeks_get_last_price by explaining that `latest` is what that sibling returns.

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?

Gives clear selection context: intraday 5m by default for the session (today or `date`), daily bars when `days` > 1 or interval is D, and `limit` keeps only the newest. It lacks an explicit 'use X instead when...' routing statement for the other historical/board siblings, so it stops short of a 5.

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

All QuantGeeks GEX 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?