Skip to main content
Glama

get_stock_read_live

Read-only

Is NVDA a buy right now, on the live board? One name, read before any buy: buy, wait or chase, its band, entry window, hold label and leader flag. One stock's current-session scores and entry state, including the live coil read (coil_score / coil_kind / coil_note). Includes tr when the name is rated: the technical rating's day and swing verdicts and how many of their timeframes agree (new: its graded record starts now). 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. Live version. Coil Live is a subscription with a 7-day free trial; subscribers connect the Coil Live connector and sign in, and this read returns live data. Agents with an x402 wallet can also pay per call. Without a subscription or an x402 wallet it returns a PaymentRequired object and no data.

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_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker, e.g. NVDA

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already mark this read-only, open-world, non-idempotent and non-destructive, so the safety profile is covered. The description goes further by disclosing the payment gate and its failure mode ('returns a PaymentRequired object and no data'), which is exactly the kind of behavior an agent cannot infer from annotations. It stops short of describing pagination, latency, or freshness guarantees.

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 lead question is well front-loaded, but the body is a run-on mix of field enumerations, jargon tokens ('coil_score / coil_kind / coil_note', 'dip: {ok, codes, setup}') and a 'Live version.' fragment that repeats the 'live board' framing. Because there is no output schema, some field listing earns its place, but the packing makes it harder to scan than it needs to be.

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 and a rich nested return, the description does the necessary work: it explains the tr and dip blocks and when dip is present, and it covers the payment failure path. Only the meaning of domain terms like 'band', 'coil', and 'entry-quality and depth floors' is left unexplained.

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 a single parameter with 100% schema description coverage ('Ticker, e.g. NVDA'), so the schema already carries the semantics. The description adds no format rules, normalization, or failure behavior for an unknown ticker, so the baseline of 3 applies.

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 names a specific verb and resource ('One stock's current-session scores and entry state') and frames the question it answers ('Is NVDA a buy right now, on the live board?'). It enumerates the payload (buy/wait/chase, band, entry window, hold label, leader flag), so its scope is clear. It never names the non-live sibling get_stock_read as the alternative, leaving the live-vs-delayed split to the phrase 'Live version.'

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?

'One name, read before any buy' gives a concrete when-to-use context, and the closing sentences state the access preconditions (subscription, x402 wallet) that gate a successful call. It does not state when to prefer it over get_stock_read or get_technical_rating_live, but it does supply clear operating context.

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