massive-mcp

Overview Schema Source Related Servers Discussions Admin

get_daily_ticker_summary

Retrieve daily open, high, low, and close prices for any stock ticker on a specific date. Also supports split-adjusted values.

Instructions

Daily open/high/low/close for a single ticker on a given date.

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": {
      "ticker": "<ticker>",
      "date": "<date>"
    },
    "name": "get_daily_ticker_summary"
  }
}

Input Schema

Name	Required	Description
`ticker`	Yes	Stock symbol.
`date`	Yes	"YYYY-MM-DD".
`adjusted`	No	Adjust for splits. Default true.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 8, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states what data is returned but does not mention that it is a read-only operation, potential rate limits, error handling for missing tickers, or any side effects.

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?

The description is a single, clear sentence that immediately states the core function. It wastes no words and is perfectly front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has a simple purpose and an output schema (known from context), so the description need not detail return values. However, it lacks usage context relative to many similar sibling tools and gives no hints about typical use cases or limitations.

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?

The input schema covers all three parameters with descriptions (100% coverage). The tool description adds minimal additional context beyond 'single ticker on a given date', which is already implicit in the schema. 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 clearly and specifically states that the tool returns daily open/high/low/close data for a single ticker on a given date. This distinguishes it from siblings like get_aggregates (which may provide multi-day bars) and get_previous_close (single value).

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?

The description does not provide any guidance on when to use this tool versus its siblings (e.g., get_aggregates for multi-day or intraday data, get_snapshot for current day). No when-to-use or when-not-to-use information is given.

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