Skip to main content
Glama

market-data

by ai.marketcrew
OverviewDiscussionsAdmin

Technical indicators

get_technical_indicators
Read-onlyIdempotent

Calculate technical indicators for a ticker: SMA(50/200), RSI(14), MACD, ATR(14), ADX(14) trend strength, Stochastic(14,3), volume (OBV trend + volume vs 20-day average), RSI/price divergence, Golden/Death Cross, and RSI regime. Computed from daily price history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesTicker symbol, e.g. 'SPY'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNo
closeNo
tickerNo
weeklyNo
signalsNo
positionNo
range_52wNo
indicatorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedOutput schema / properties / close / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
    • changedOutput schema / properties / date / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / indicators / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / position / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / range_52w / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / signals / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
    • changedOutput schema / properties / ticker / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / weekly / type
      Previous value: -"object"New value: +[
+  "object",
+  "null"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "close": {
+      "type": "number"
+    },
+    "date": {
+      "type": "string"
+    },
+    "indicators": {
+      "type": "object"
+    },
+    "position": {
+      "type": "object"
+    },
+    "range_52w": {
+      "type": "object"
+    },
+    "signals": {
+      "type": "object"
+    },
+    "ticker": {
+      "type": "string"
+    },
+    "weekly": {
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, covering the safety profile. The description adds that indicators are computed from daily price history, which is useful context about data granularity, but does not disclose rate limits, auth requirements, or error behavior.

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?

The description is a single front-loaded sentence that immediately states the action and resource before listing the computed indicators. Every item in the list contributes to scope, and there is no filler or redundancy.

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?

For a read-only calculation tool with one required parameter, full schema coverage, rich annotations, and an output schema, the description is nearly complete. It fully enumerates what is computed and the data source, though it omits usage context that would help in a suite with many related market-context siblings.

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?

There is only one parameter, ticker, and schema description coverage is 100% with the example 'SPY'. The description says 'for a ticker' but adds no syntax or format detail beyond what the schema already provides, matching the baseline for high schema coverage.

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 (Calculate) and resource (technical indicators for a ticker) and lists the exact indicators computed, making the tool's scope unambiguous. It does not explicitly name or differentiate itself from sibling tools such as get_price_history or get_ta_methodology, which keeps it from a 5.

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 gives no guidance about when to use this tool versus alternatives like get_price_history, get_key_levels, or get_ta_methodology. Usage is only implied by the tool's name and purpose, with no stated context or exclusions.

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

All market-data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources