Skip to main content
Glama

fetch_macd

[Personal research only] Fetch MACD (Moving Average Convergence Divergence) technical indicator time series with signal line and histogram.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesStock ticker symbol (e.g., 'AAPL', 'MSFT', 'TSLA') for which to calculate MACD
datatypeNoResponse data type.json
end_dateNoOptional end date filter in YYYY-MM-DD format (e.g., '2024-12-31').
intervalYesTime interval for data points.
fastperiodNoFast EMA period for MACD calculation (default: 12)
slowperiodNoSlow EMA period for MACD calculation (default: 26)
start_dateNoOptional start date filter in YYYY-MM-DD format (e.g., '2024-01-01').
series_typeNoPrice data to use for calculation.close
signalperiodNoSignal line EMA period for MACD calculation (default: 9)
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, the description carries the full burden and discloses almost nothing behavioral: no mention of rate limits, authentication or entitlement requirements (the '[Personal research only]' note hints at a restriction but never states it), no note that values are computed server-side from price data, and no indication of pagination or truncation despite a max_data_points parameter. It only adds that the series includes a signal line and histogram.

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 named immediately and no filler. The bracketed '[Personal research only]' prefix comes first, which is slightly awkward placement for a caveat but is short enough not to obscure the purpose.

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 a 10-parameter indicator tool with no output schema and no annotations, the description should at minimum sketch the return shape or note interval/date-filter behavior. It does name the three output series, which is the main thing an agent needs, but leaves the interval value domain, default behavior, and entitlement constraints unexplained.

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 every parameter including fastperiod, slowperiod, and signalperiod is already documented, and the description adds no syntax or constraint detail beyond that. Baseline 3 is appropriate; the mention of 'signal line' loosely reinforces the signalperiod semantics but nothing more.

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?

States a specific verb (Fetch) and resource (MACD technical indicator time series) and names the components returned (signal line, histogram), which distinguishes it from sibling indicator tools such as fetch_rsi, fetch_ema, and fetch_bbands. It does not explain how it relates to the more general fetch_time_series_* or analyze_stock tools, but the indicator identity is unambiguous.

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?

There is no statement of when to choose MACD over RSI, EMA, or SMA, nor any prerequisites or exclusions. The only usage-flavored text is a bracketed '[Personal research only]' tag that doesn't tell an agent which request should route here.

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