Skip to main content
Glama

Stock snapshot

get_stock_snapshot
Read-onlyIdempotent

Price, daily change, day and 52-week range, market cap, valuation (P/E, forward P/E, EPS, dividend yield), company profile (sector, industry, CEO, employees, description), revenue and margins, the next earnings date and the ETFs that hold it, for one stock or ETF. Includes the as-of time and source.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesTicker symbol, e.g. NVDA, SPY or BRK.B. Index symbols use ^, e.g. ^GSPC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds genuine value with 'Includes the as-of time and source', setting freshness/provenance expectations, but says nothing about partial or missing data for fields like next earnings date or ETF holders, which is the main behavioral risk for a multi-source aggregate.

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?

It is a single dense sentence that front-loads the most-used fields (price, change, range, cap) before the deeper fundamentals. The long comma-and-parenthesis chain is heavy to parse but nearly every clause carries a distinct field since no output schema exists.

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 must carry the return shape, and it does so comprehensively across price, fundamentals, profile, earnings, and ETF holdings, plus as-of time and source. The remaining gap is that it does not address failure or null-field behavior, or how it differs from the quote/history siblings.

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 coverage is 100% and the symbol parameter already documents ticker examples, BRK.B dot notation, and ^ index prefixes. The description contributes only that the target is a single stock or ETF; it adds no format or edge-case meaning beyond the schema, so baseline 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 enumerates exactly what the tool returns — price, daily change, ranges, market cap, valuation ratios, profile, revenue/margins, earnings date, ETF holders — for one stock or ETF. That is a clear, specific resource definition, though it never explicitly contrasts with neighbors like get_quotes or get_price_history, so an agent must infer the boundary from the field list alone.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. The only scoping signal is 'for one stock or ETF', which hints at single-symbol use versus batch tools but is never stated as a selection rule.

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