Skip to main content
Glama

fetch_sma

[Personal research only] Fetch Simple Moving Average (SMA) technical indicator time series with customizable time periods.

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": {
      "symbol": "<symbol>",
      "interval": "<interval>",
      "time_period": "<time_period>"
    },
    "name": "fetch_sma"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesStock ticker symbol (e.g., 'AAPL', 'MSFT', 'TSLA') for which to calculate Simple Moving Average
datatypeNoResponse data type.json
end_dateNoOptional end date filter in YYYY-MM-DD format (e.g., '2024-12-31').
intervalYesTime interval for data points.
start_dateNoOptional start date filter in YYYY-MM-DD format (e.g., '2024-01-01').
series_typeNoPrice data to use for calculation.close
time_periodYesNumber of data points to use for moving average calculation (e.g., 20 for 20-day SMA)
max_data_pointsNoMaximum number of time series data points to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 behavioral disclosure. 'Fetch' implies a read operation, and '[Personal research only]' hints at a usage restriction, but the description says nothing about data source, rate limits, pagination, or response shape for a tool that returns a multi-point time series.

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?

A single front-loaded sentence with the resource identified immediately and no padding. It is efficient, though its brevity is part of why behavioral and usage context is thin.

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?

For an eight-parameter read tool with no annotations and no output schema, the description is minimally adequate: the schema fully documents inputs, so the agent can call it, but nothing explains the returned series, pagination via max_data_points, or the practical meaning of the 'personal research only' restriction.

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 description coverage is 100%, so all eight parameters including symbol, interval, time_period, and date filters are already documented in the schema. The description adds only the vague phrase 'customizable time periods', which does not meaningfully extend what the schema provides; baseline 3 applies.

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

Purpose4/5

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

The description states a specific verb ('Fetch') and resource ('Simple Moving Average (SMA) technical indicator time series'), which is enough to distinguish it from siblings like fetch_ema, fetch_macd, and fetch_rsi by indicator type. It is clear, though it does not explicitly name the sibling alternatives it replaces.

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 offers no when-to-use guidance, no exclusions, and does not route the agent to alternatives such as fetch_ema or fetch_rsi. The only guidance is the bracketed '[Personal research only]' tag, which sets a scope but is not usage guidance for selecting this tool over another.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources