Skip to main content
Glama

quantdata

by uk.quantdata

Request a free Quant Data API key

quantdata_request_free_api_key
Idempotent

Send a free qd_ API key to an email address. No account, card, payment or GUI is required. The key covers all four market-data tools, sharing 10 successful calls per UTC day. The raw key is delivered only to the inbox and is never returned in this tool result. Ask the user for the email address before calling. Set marketing_opt_in to true only when the email owner explicitly asks to receive occasional product updates; it defaults to false and is not required for the key. A true value stays pending until the recipient replies SUBSCRIBE to the key email.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesInbox that should receive the qd_ key.
marketing_opt_inNoOptional separate consent for product-update emails.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial context beyond annotations: key is delivered only to the inbox and never returned in the tool result, the key shares 10 successful calls per UTC day across tools, and marketing_opt_in remains pending until the recipient replies SUBSCRIBE. These details meaningfully enrich the behavioral understanding.

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?

Seven sentences, each contributing relevant information without fluff. The main action is front-loaded, and the structure logically flows from what the tool does to prerequisites to parameter nuances. Slightly verbose but well-organized.

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?

Comprehensive coverage of prerequisites, side effects, rate limits, and the key's non-return. The only minor gap is not stating what the tool result actually contains (e.g., a success message), but the description explicitly clarifies what it does not contain.

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% with clear descriptions for both parameters. The description adds value by specifying that the key is 'free', delivered only to the inbox, and provides consent-wording expectations ('only when the email owner explicitly asks') plus the pending state behavior for marketing_opt_in.

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 clearly states 'Send a free qd_ API key to an email address' with a specific verb and resource. It distinguishes itself from the sibling market-data tools by explaining that the key covers all four tools, making the tool's role as an access-granting step explicit.

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?

Provides explicit prerequisites: 'Ask the user for the email address before calling' and clear consent instructions for marketing_opt_in. It does not explicitly name alternatives or exclusions, but the purpose is distinct enough to infer when to use it.

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

All quantdata toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool targets a distinct market data domain: Brooks price action events, dealer gamma, options max pain, API key request, and Weis Wave volume-price structure. Despite some conceptual overlap between options-related tools, their descriptions clearly differentiate calculations and data sources.

Naming Consistency5/5

All five tools follow the exact same `quantdata_<topic>` snake_case pattern, making the naming perfectly uniform and predictable. No mixed conventions or stylistic deviations.

Tool Count5/5

Five tools is a well-scoped set for a specialized quant data server. Each tool serves a clear analytical purpose, and the API key request tool supports access to the four data tools without bloating the surface.

Completeness5/5

The set explicitly covers four market-data categories plus key management, and each tool is fully self-contained for its intended analysis. No obvious dead ends or missing core operations within the stated domain of quantitative market analytics.

Resources