Skip to main content
Glama

compute_indicators

Calculate SMA, EMA, RSI, or ATR values for an NSE symbol over a time range, using prior-candle warm-up to avoid look-ahead bias. Specify periods per indicator to get accurate technical values.

Instructions

Calculate SMA, EMA, RSI, or ATR values with prior-candle warm-up and no look-ahead.

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": {
      "arguments": "<arguments>"
    },
    "name": "compute_indicators"
  }
}

Input Schema

NameRequiredDescriptionDefault
argumentsYes

Output Schema

NameRequiredDescriptionDefault
valuesYes
returned_countYes
indicator_statusYes
indicator_parametersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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. It usefully discloses that prior candles are consumed for warm-up and that values avoid look-ahead, but says nothing about what that means in practice (leading nulls in output, errors on insufficient history), permission or rate-limit behavior, or cost. Two behavioral hints do not cover a computational data tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with no padding, which is good. However, its brevity is achieved by omitting substantive information, so the economy is partly under-specification rather than disciplined concision.

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?

An output schema exists, so return-shape explanation is not required, and the request/response contract is largely defined by the input schema. Still, warm-up semantics are the tool's defining subtlety and are left as a bare phrase, leaving an agent unclear on what a shorter-than-expected result or leading gaps mean.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is reported at 0%, so the description is expected to compensate. It never mentions symbol, start/end datetime, or how the optional periods map to the requested indicators, and it does not clarify the interaction between the warm-up limit and the period values.

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 (Calculate) and resource (SMA, EMA, RSI, ATR values), which clearly separates it from the sibling data-fetch tools like get_bars or get_price_extremes. It does not explicitly name an alternative, but the enumerated indicator set makes the tool's identity unmistakable.

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 when-to-use or when-not-to-use guidance, no mention of prerequisites such as symbol availability or minimum history length, and no comparison to sibling tools. The clause about warm-up and look-ahead is behavioral, not usage guidance.

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