Skip to main content
Glama
portfolio-signals-mcp

portfolio-signals-mcp

get_technical_signals

Computes RSI, MACD, and SMA 50/200 relationships for a ticker, returning threshold classifications so callers can interpret momentum and trend signals.

Instructions

Compute technical indicators for a ticker: RSI(14), MACD(12,26,9), and SMA 50/200 relationships.

Returns measurements and standard threshold classifications only — interpretation is left to the caller. Classifications used:

  • rsi_zone: 'overbought' if RSI >= 70, 'oversold' if RSI <= 30, else 'neutral' (standard Wilder thresholds)

  • macd.vs_signal: MACD line position relative to its 9-period signal line, including single-day crossovers

  • moving_averages.sma_50_vs_200: 'golden_cross' if SMA50 > SMA200, 'death_cross' otherwise (standard definitions)

Args: ticker: Symbol like 'AAPL', 'NVDA'.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_technical_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the exact thresholds used for rsi_zone, macd.vs_signal, and sma_50_vs_200, and explicitly limits output to 'measurements and standard threshold classifications only'. Gaps remain around data freshness (real-time vs delayed), required lookback history, and error behavior for an unknown ticker.

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?

Front-loaded with the purpose, then a compact output-contract section, then the arg note. Every line earns its place, especially the threshold definitions, which substitute for the absent output schema.

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 one-parameter tool with no output schema and no annotations, the definition is nearly self-sufficient: it explains what is returned and how values are classified. The remaining omission is operational context such as data source, delay, and history requirements.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it does provide format guidance via examples ('AAPL', 'NVDA') for the single ticker parameter. It adds no constraint on exchange suffix or symbol format beyond those examples.

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?

States a specific verb and resource ('Compute technical indicators for a ticker') and enumerates exactly which indicators are produced (RSI(14), MACD(12,26,9), SMA 50/200), which sharply delimits scope against siblings like get_quote or compare_tickers.

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: an agent can infer this is the tool for indicator-based analysis, and the line 'interpretation is left to the caller' clarifies the boundary of responsibility. There is no explicit when-to-use/when-not guidance or reference to an alternative (e.g., when a plain price lookup suffices).

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