Skip to main content
Glama

FinanceQuery

Technical Indicators

get_indicators
Read-onlyIdempotent

Get all 42 technical analysis indicators (SMA, EMA, RSI, MACD, Bollinger Bands, Ichimoku, etc.) for one or more stock symbols (comma-separated). A single symbol returns one indicators object; multiple symbols return a paginated batch plus per-symbol errors.

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": {
      "symbols": "<symbols>",
      "interval": "<interval>",
      "range": "<range>"
    },
    "name": "get_indicators"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum symbols per page (only applies when multiple symbols given); omitted = curated default (25)
rangeYesTime range: 1mo|3mo|6mo|1y|2y|5y (default: 1y)
cursorNoOpaque continuation token from a previous response's `pageInfo.endCursor`; omitted = first page
fieldsNoComma-separated list of GraphQL field names to include; omitted = curated default set
symbolsYesOne or more comma-separated ticker symbols (e.g., "AAPL" or "AAPL,MSFT,GOOG")
intervalYesCandle interval: 1d|1wk|1mo (default: 1d)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety bar is low. The description goes beyond them by disclosing the two response modes (single object vs paginated batch) and that multi-symbol calls can return per-symbol errors, which materially affects how an agent plans a batch request.

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?

Two sentences, zero filler, with the capability and the indicator set front-loaded and the return-shape caveat following. Every clause carries operational information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six parameters at full schema coverage and no output schema, the description covers the main risk (batch mode pagination and partial failures) and names the indicator family. It stops short of describing the indicator object's fields or the curated default set, which an agent calling without `fields` might want to know.

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 symbols, interval, range, limit, cursor and fields are already documented individually. The description only reinforces the comma-separated symbol format and hints that batching relates to pagination; it adds no syntax, default, or constraint meaning beyond the schema, so the baseline of 3 applies.

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?

Specific verb plus resource: 'Get all 42 technical analysis indicators' with a concrete enumeration (SMA, EMA, RSI, MACD, Bollinger Bands, Ichimoku) and an explicit input scope ('one or more stock symbols'). That enumeration makes it distinguishable from data-retrieval siblings such as get_chart or get_analysis without opening a schema.

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?

Usage is only implied: fetch indicators when you need computed technical studies for a ticker. There is no statement of when to prefer this over get_chart or get_analysis, no prerequisites, and no exclusion about supported asset classes despite openWorldHint=true.

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.