Skip to main content
Glama
drmartell

thetadata-mcp

by drmartell

stock_at_time_quote

Get the last bid/ask quote for a stock at a specific time of day, with optional start and end dates for historical data retrieval.

Instructions

[VALUE] Last quote at a specific time of day for a stock.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
venueNoUsed to specify the venue of the real time or historic request. ``nqb`` = Nasdaq Basic; ``utp_cta`` = merged UTP & CTA.nqb
symbolYesThe stock or index symbol, or underlying symbol for options.
end_dateNoThe end date (inclusive).
start_dateNoThe start date (inclusive).
time_of_dayYesThe time of the day to fetch data for; assumed to be America/New_York.
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It fails to explain what 'last quote' means (e.g., close vs. latest), timezone nuances beyond the schema, or behavior when no data exists for the specified time. The schema adds a timezone assumption, but the description adds no behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no fluff. It states the core value proposition directly, making it appropriately concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 5 parameters, no output schema, and no annotations. The description is extremely minimal for a temporal query tool, omitting information about optional date parameters, return value structure, and edge cases. This leaves significant gaps for an agent attempting to use the tool correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so all parameters are individually documented. The description does not add extra semantics beyond the schema, but the baseline of 3 applies because the schema handles parameter documentation adequately.

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?

The description states the tool returns the 'last quote at a specific time of day for a stock,' which clearly identifies the resource (stock quote) and the temporal specificity. It distinguishes from trade and history tools by the quote and at-time focus, though it does not explicitly differentiate from snapshot tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidance is provided. The description does not indicate when to use this tool over siblings like stock_snapshot_quote or stock_history_quote, nor does it offer any exclusions or alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/drmartell/thetadata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server