QuantGeeks GEX

Look up the reading guide

quantgeeks_lookup_guide

Read-onlyIdempotent

Without signing in: the basic reading guide: the core terms and the rules for reading the data correctly. Signed in with a free QuantGeeks account: the basic reading guide: the core terms and the rules for reading the data correctly. With a QuantGeeks plan: the complete guide: the full course, the field manual, and every term, rule and checklist. Reading rules for QuantGeeks data; call it before interpreting a board. With query (a term such as primary node, gamma flip, roll, VEX, or any words) it returns the entry or the closest sections, each with an id. With section (an id from a previous lookup) it returns that whole section. Give exactly one. It never labels a pattern itself.

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": "quantgeeks_lookup_guide"
  }
}

Input Schema

Name	Required	Description	Default
`query`	No
`section`	No

Output Schema

Name	Required	Description	Default
`id`	No
`more`	No
`note`	No
`term`	No
`text`	No
`tier`	No
`as_of`	Yes
`found`	No
`match`	No
`query`	No
`title`	No
`access`	Yes
`notice`	Yes
`source`	Yes
`symbol`	Yes
`account`	No
`preview`	Yes
`results`	No
`pro_plan`	No
`truncated`	No
`definition`	No
`subsections`	No
`truncated_more`	No
`related_sections`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, and the description adds genuinely new context: the response depth is gated by auth tier (anonymous, free account, paid plan). It also discloses a capability boundary — 'It never labels a pattern itself' — which prevents the agent from expecting interpretation output.

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 tier preamble front-loads the access model well, but it repeats 'the basic reading guide: the core terms and the rules for reading the data correctly' verbatim twice for anonymous and free tiers. That duplication wastes space that could have carried the access-model point once with a single qualifier.

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?

Complete enough for invocation: both parameters are explained, the two lookup modes are distinguished, the tier gating is disclosed, and an output schema exists so return shapes needn't be described. Only minor gaps (no note on what happens if neither parameter is supplied) remain.

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 description coverage is 0%, so the description carries the full burden and does so: `query` is defined as a term like primary node, gamma flip, roll, VEX or free words returning matching entries/sections with ids, and `section` is defined as an id from a previous lookup returning that full section. The 'Give exactly one' constraint is also stated.

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?

States a specific verb and resource (look up the reading guide / glossary and reading rules) and enumerates what the tiers return. It implicitly separates itself from analytical siblings via 'call it before interpreting a board' and 'It never labels a pattern itself', though no sibling is named explicitly.

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?

'Reading rules for QuantGeeks data; call it before interpreting a board' gives a clear when-to-use trigger and ordering relative to other analysis tools. It doesn't state when to skip it or name a specific alternative for term lookups, so it stops short of full routing guidance.

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?