massive-mcp

Overview Schema Source Related Servers Discussions Admin

get_all_snapshots

Retrieve real-time snapshots for US stocks, with optional ticker filtering to limit data size.

Instructions

Real-time snapshot for multiple/all US stocks. Use tickers to filter — calling with no filter returns the entire market and may be very large.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_all_snapshots"
  }
}

Input Schema

Name	Required	Description	Default
`tickers`	No	Optional list of symbols. If None, returns all.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 8, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'Real-time' and gives a size warning, but lacks disclosure on rate limits, data freshness, what a 'snapshot' includes, or any potential side effects. For a tool with no annotations, this is insufficient.

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?

Two sentences provide clear purpose and usage note. No extra words, front-loaded, and every sentence adds value. Ideal conciseness.

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?

Given the presence of an output schema, return values need not be described. The description covers purpose and key usage warning. It could briefly mention that it's real-time, but that is implied. A small gap is lack of explicit differentiation from siblings beyond the scope phrasing.

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 description adds context about filtering and the large result when no filter is applied. This reinforces the schema's description but does not add new semantic depth beyond usage guidance. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'get' and resource 'snapshot' with clear scope 'multiple/all US stocks'. It distinguishes from the sibling 'get_snapshot' which is singular, and from other data retrieval tools like 'get_quotes' and 'get_trades'.

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?

The description clearly explains that the 'tickers' parameter is for filtering and warns that calling with no filter returns the entire market which can be large. This provides explicit usage context, though it does not name alternative tools or state when not to use this tool.

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