massive-mcp

Overview Schema Source Related Servers Discussions Admin

get_previous_close

Retrieve the previous trading day's open, high, low, and close prices for a stock ticker, optionally adjusted for splits.

Instructions

Previous trading day's OHLC for a single stock ticker.

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>"
    },
    "name": "get_previous_close"
  }
}

Input Schema

Name	Required	Description	Default
`ticker`	Yes	Stock symbol (e.g. "NVDA").
`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

A3.5/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 the full burden. It only states the basic purpose, omitting behavioral traits like limitations (e.g., market holidays, timezone), the meaning of the 'adjusted' parameter, or that only OHLC is returned. Minimal transparency.

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?

The description is a single concise sentence with no waste, front-loading the key action. However, it may be slightly under-specified for a tool with two parameters and no additional context.

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, the description need not explain return values. It adequately covers the basic purpose and ticker constraint. Lacks details on data bounds but is sufficient for a simple 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?

Schema coverage is 100%, and the description adds no new meaning beyond 'single stock ticker' and 'previous trading day's OHLC.' The schema already describes parameters adequately, so the description adds minimal value.

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 states it retrieves the previous trading day's OHLC for a single stock ticker, which is a specific verb and resource. It distinguishes from siblings like get_aggregates (multi-day) and get_last_quote (real-time).

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?

The description implies usage for a single ticker and previous day's data, but provides no explicit guidance on when to use it versus alternatives. Sibling tool names are given but no comparisons or when-not-to-use conditions.

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