Skip to main content
Glama

fetch_rsi

[Personal research only] Fetch RSI (Relative Strength Index) momentum oscillator time series ranging from 0 to 100.

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

Input Schema

NameRequiredDescriptionDefault
symbolYesStock ticker symbol (e.g., 'AAPL', 'MSFT', 'TSLA') for which to calculate RSI
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_periodNoNumber of periods for RSI calculation (typically 14)
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 burden. 'Fetch' implies a read, but it discloses nothing about output shape, rate limits, error conditions, or what happens with large date ranges — only the value range of the returned series.

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 scope caveat first and the resource definition second; no wasted text. It is short partly because it omits useful detail rather than because it is dense.

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 an 8-parameter tool with no output schema and no annotations, the description says nothing about how interval values are constrained (no enums), how max_data_points interacts with date filters, or what the response contains structurally. The schema covers the parameters, but the behavioral envelope is thin.

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 itself documents all eight parameters including defaults for time_period and max_data_points. The description adds essentially no parameter-level meaning beyond the 0-100 output range, so baseline 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?

States a specific verb (fetch) and resource (RSI momentum oscillator time series) and adds the meaningful 0-100 bound. It distinguishes itself from indicator siblings (fetch_ema, fetch_macd, fetch_sma, fetch_bbands) only by naming the indicator, with no explicit contrast statement.

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 guidance and no mention of the sibling indicator tools that are the obvious alternatives. The bracketed '[Personal research only]' is a scope caveat, not invocation guidance.

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