Skip to main content
Glama

TradingMCP

by io.github.atilaahmettaner
OverviewDiscussionsAdmin

Extended-Hours Stock Price

stock_extended_hours
Read-only

Real-time pre-market and after-hours prices for a US stock symbol.

Use this when the user asks about a stock outside the regular 9:30am-4pm
ET session — earnings reactions, overnight news, "what is X doing in
after-hours?", "how did Y open in pre-market?". Returns the most recent
valid print from each session window (pre-market, regular, post-market)
along with computed % changes vs. the previous close and the regular
close, respectively.

During the regular session, post_market will be null (no data yet).
On weekends/holidays, returns whatever's most recent in each window.

Args:
    symbol: US stock symbol — AAPL, NVDA, TSLA, SPY, ^GSPC, etc.

Returns:
    - pre_market: {price, as_of_utc, change_vs_previous_close_pct, reference_close} or null;
      the change is measured from reference_close, the last regular close
      (before the open that is newer than previous_close)
    - regular: {price, as_of_utc, change_pct} (consolidated tape close)
    - post_market: {price, as_of_utc, change_vs_regular_close_pct} or null
    - previous_close, currency, exchange, market_state for context

Input Schema

NameRequiredDescriptionDefault
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, non-destructive, open-world); the description adds genuinely non-obvious behavior: post_market is null during the regular session, weekend/holiday calls fall back to the latest print per window, and how the % change is anchored to reference_close vs. the regular close. That is exactly the context an agent needs to interpret a sparse-looking response.

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-loaded trigger sentence, then example queries, then behavior and return shape — well ordered and mostly waste-free. The reference_close explanation ('before the open that is newer than previous_close') is dense and takes a re-read, which slightly undercuts clarity.

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?

With no output schema, the Returns block is necessary and covers the field names, nullability, and change semantics, making the response interpretable. The remaining gap is error behavior for invalid or non-US symbols, which the description silently assumes away.

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?

The schema is a bare string with 0% description coverage, so the description must compensate; it does so with concrete accepted forms (AAPL, NVDA, TSLA, SPY, ^GSPC), which clarifies that indices/caret symbols are allowed. It does not say whether exchange-qualified or non-US symbols are rejected.

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/resource pair ('real-time pre-market and after-hours prices for a US stock symbol') and bounds it to the extended session, so an agent can tell it apart from regular-session quote siblings like stock_prices or yahoo_price. It never names those siblings, so the differentiation is implicit rather than 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?

Gives a concrete trigger condition ('when the user asks about a stock outside the regular 9:30am-4pm ET session') plus worked example phrasings such as 'what is X doing in after-hours?'. Clear about when to use, but never states the complement — i.e. which tool to reach for during the regular session.

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

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