Skip to main content
Glama

alpha-sentinel-mcp

analyze_volatility

Analyze price volatility using statistical Z-score anomaly detection.

Calculates standard deviations from mean price to detect anomalous movements. Configurable thresholds and time windows for customized analysis.

Use Case: Identify unusual price movements before they become obvious trends.

Cost: $0.02 USD per call

Parameters:

  • symbol: Crypto symbol to analyze

  • window_minutes: Historical window (1-1440 min, default: 60)

  • z_threshold: Std dev threshold for anomalies (0.1-5.0σ, default: 2.0)

Alert Levels: NORMAL → MODERATE → HIGH → CRITICAL

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>"
    },
    "name": "analyze_volatility"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesCryptocurrency symbol
z_thresholdNoZ-score threshold for anomalies
window_minutesNoAnalysis window in minutes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real operational context: a $0.02 per-call cost and a NORMAL/MODERATE/HIGH/CRITICAL alert ladder that hints at output shape. It does not describe return payload contents (per-anomaly timestamps, z-values), data source, or failure behavior, which is a meaningful gap for an unannotated analytical tool.

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?

The description is front-loaded with the core purpose in the first sentence and organized with clear labeled sections for use case, cost, parameters, and output levels. The parameter list duplicates the schema verbatim, which is the main piece of dead weight, but nothing else is padded.

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 a simple three-parameter analysis tool with no output schema, the description covers cost, method, parameter ranges, and an alert-level taxonomy, which is reasonably complete. What is missing is any statement of what a call actually returns (the z-scores, thresholds crossed, affected window) or prerequisites on the symbol format, so an agent cannot fully anticipate results.

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 all three parameters are already documented structurally, establishing a baseline of 3. The description largely restates the schema's ranges and defaults, adding only mild interpretive value ('Std dev threshold for anomalies', the σ unit, and the 'Historical window' framing).

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 and resource plus the method: 'Analyze price volatility using statistical Z-score anomaly detection.' Combined with 'Calculates standard deviations from mean price,' an agent knows exactly what computation happens. It does not explicitly contrast with siblings like calculate_risk_score, keeping it below 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Use Case' line gives situational context ('identify unusual price movements before they become obvious trends'), which implies when the tool is valuable. However, there is no explicit when-not guidance and no routing to or from alternatives such as calculate_risk_score or fetch_price, leaving the agent to infer the boundary.

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.