Skip to main content
Glama

get_stock_read

Read-onlyIdempotent

Is NVDA a buy? One name, read before any buy: buy, wait or chase, its band, entry window, hold label and leader flag. One stock's Coil read, headline fields: its board-percentile band (the highest 5%, the highest 10%, the highest quartile, middle half or lowest quartile), entry window (READY or SETUP when the name is on its book's scored pick list; otherwise the day board's state, such as WAIT, CHASE, BASING or FALLING, for names on the day board; null with a note when neither lists it), hold label, leadership flag, price move, trading days to the next earnings report and its book's regime. Covers any S&P 500, Nasdaq-100 or macro name, one symbol per call; unknown symbols return the valid-symbol directory. dip: {ok, codes, setup}: present only for oversold-pullback candidates; a dip buy only on a completed hourly turn above the entry-quality and depth floors. Free sample: one symbol per call, headline fields, from the morning read.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker, e.g. NVDA

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/no-side-effects, and the description adds real behavior beyond them: unknown symbols return the valid-symbol directory, the entry-window field is null with a note when neither the book nor day board lists the name, and the `dip` object appears only for oversold-pullback candidates with an explicit gating rule. It stops short of describing response shape or size, but the conditional and null-case behavior is unusually well disclosed.

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 intent is front-loaded and the field list is informative, but the prose is a dense run-on with heavy nested parentheses (the band and entry-window enumerations) that an agent must parse in one pass. The field dump could have been tightened considerably without losing meaning.

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 description carries the return-value burden and largely meets it by enumerating the headline fields and the conditional `dip` object. It also states the covered universe (S&P 500, Nasdaq-100, macro names), which is sufficient for a single-parameter read tool.

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?

There is one parameter with 100% schema coverage ('Ticker, e.g. NVDA'), so the schema already does the documentation work. The description adds only the constraint of one symbol per call and the error path for invalid symbols, which is useful but minimal.

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 uses a concrete verb+resource: it reads one stock's Coil/headline fields (band, entry window, hold label, leadership flag, price move, earnings days, regime) for a single symbol per call. The opening 'Is NVDA a buy?' frames intent well, but the term 'Coil read' is unexplained jargon and there is no differentiation from the sibling get_stock_read_live.

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

Usage Guidelines3/5

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

'read before any buy' and 'one symbol per call' imply a pre-purchase screening use case, and the free-sample framing hints at a scope limit. However, no alternative tool is named and no conditions distinguish this static read from get_stock_read_live or get_day_board, leaving the agent to infer routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources