massive-mcp

Overview Schema Source Related Servers Discussions Admin

get_sma

Calculate the simple moving average for a stock using historical price data. Specify ticker, timespan, window, and series type to get SMA values.

Instructions

Simple Moving Average indicator values for a stock.

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

Input Schema

Name	Required	Description	Default
`ticker`	Yes	Stock symbol.
`timespan`	No	Bar interval. Default "day".	day
`window`	No	Lookback window. Default 50.
`series_type`	No	Price series for calculation. Default "close".	close
`timestamp`	No	Reference timestamp (date or unix); default = now.
`limit`	No	Max rows. Default 50.
`cursor`	No	Pagination cursor.

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?

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only states 'indicator values' without explaining potential data sources, calculation specifics, or limitations (e.g., rounding, adjustment). For a technical indicator, 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?

A single sentence that is direct and devoid of fluff. Every word contributes to conveying the tool's purpose, achieving maximum conciseness.

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?

Output schema exists, reducing the need to describe returns, but the description still omits context like time-series behavior, pagination hints, or how to interpret results. Given the numerous sibling tools with similar parameters, more context would aid selection.

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%, so baseline is 3. The description adds no extra meaning beyond the schema; parameters are well-documented in the schema itself. The description does not clarify parameter interactions or provide examples.

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 'Simple Moving Average indicator values for a stock,' using a specific verb ('get') and resource ('SMA values'). It distinguishes from siblings like 'get_ema' and 'get_macd' by specifying SMA, making the purpose unambiguous.

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?

No explicit guidance on when to use this tool versus alternatives such as 'get_ema' or 'get_macd.' The name implies it's for SMA, but the description lacks direct comparison or context for selection.

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