Skip to main content
Glama

fetch_ema

[Personal research only] Fetch Exponential Moving Average (EMA) technical indicator time series with greater weight on recent prices.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesStock ticker symbol (e.g., 'AAPL', 'MSFT', 'TSLA') for which to calculate Exponential 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., 12 for 12-period EMA)
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?

No annotations are provided, so the description carries the full behavioral burden, yet it only implies the tool is read-only and returns a series. It says nothing about data source/licensing behind the 'personal research only' caveat, rate limits, error behavior for invalid symbols, or how the series is paginated by max_data_points.

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 compact sentence pairs the action with the indicator definition, with no wasted words. The bracketed disclaimer sits first, which slightly delays the actual purpose but is still brief.

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?

With 8 parameters, no annotations, and no output schema, the schema alone must carry most of the specification, which it does at 100% coverage. The description hints at return shape ('time series') but doesn't clarify interval units or datatype options, leaving the definition adequate but not fully self-contained.

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 the schema already documents all eight parameters including interval, series_type, and date filters. The description adds only the conceptual meaning of EMA weighting, not parameter-level detail, so the baseline of 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 and resource ('Fetch Exponential Moving Average (EMA) technical indicator time series') and even characterizes the indicator ('greater weight on recent prices'), which implicitly separates it from fetch_sma. It stops short of naming the sibling tool the agent should use for simple moving averages, so it isn't fully differentiated.

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 only guidance is the '[Personal research only]' tag, which communicates a scope constraint but not when to choose EMA over fetch_sma, fetch_macd, or fetch_rsi. There are no explicit when/when-not conditions or alternatives mentioned.

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