massive-mcp

Overview Schema Source Related Servers Discussions Admin

get_ticker_overview

Retrieve comprehensive reference details for a stock ticker, including name, exchange, sector, market cap, and description.

Instructions

Reference details for a ticker: name, exchange, sector, market cap, description, etc.

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

Input Schema

Name	Required	Description	Default
`ticker`	Yes	Stock symbol.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 8, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations provided. The term 'reference details' implies a read-only operation, but the description does not explicitly confirm no side effects or mention any access considerations.

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?

Single sentence, completely front-loaded with essential information, no wasted words.

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

Completeness5/5

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

With one required parameter and an output schema (implied), the description provides sufficient context for a simple reference tool. Lists example fields for clarity.

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 covers the single parameter with 'Stock symbol.' The description lists output fields but adds no new meaning to the parameter itself. Baseline 3 as coverage is 100%.

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?

Description clearly states it provides reference details (name, exchange, sector, market cap, description) for a ticker, distinguishing it from sibling tools like get_financials or get_snapshot that focus on other data types.

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?

Implies use when needing static reference info about a ticker, but lacks explicit guidance on when to use this instead of alternatives like get_snapshot or get_financials.

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