Skip to main content
Glama
Alpha Sentinel Market Intelligence MCP

Alpha Sentinel Market Intelligence MCP

calculate_risk_score

Read-onlyIdempotent

Assess crypto position risk using volatility, liquidity, market cap tier, and BTC correlation to produce a 0–1 score with recommendations for position sizing and stop-loss levels.

Instructions

Calculate multi-factor risk assessment for cryptocurrencies.

Combines volatility, liquidity, market cap tier, and Bitcoin correlation into a comprehensive risk score (0-1 scale) with actionable recommendations.

Use Case: Assess position sizing and stop-loss levels.

Cost: $0.03 USD per call

Risk Levels: LOW | MEDIUM | HIGH | CRITICAL

Factors Analyzed:

  • Volatility risk (40% weight)

  • Liquidity risk (25% weight)

  • Market cap tier (20% weight)

  • BTC correlation (15% weight)

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

Input Schema

NameRequiredDescriptionDefault
symbolsYesList of crypto symbols to assess
include_factorsNoRisk factors to analyze

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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 behavior, and the description adds genuinely useful context beyond that: a $0.03 per-call cost, the 0-1 output scale, the four risk levels, and the factor weighting. It does not say whether the result is per-symbol or aggregated, so an agent cannot fully anticipate the response shape given there is no output schema.

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 purpose and scoring model are front-loaded, and the bolded labels (Use Case, Cost, Risk Levels, Factors Analyzed) make it scannable. Every line carries decision-relevant information — cost, output scale, factor weights — with no filler.

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 two-parameter read-only tool with no output schema, the description covers cost, output scale, categorical output levels, and factor weighting, which is close to sufficient. The remaining gap is response structure — whether scores are returned per symbol and what 'actionable recommendations' look like.

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 coverage is 100%, so both parameters are already documented and the baseline of 3 applies. The description adds meaning by explaining the weights behind the factors, but it also introduces a 'market cap tier (20% weight)' factor that is not selectable in the include_factors enum (only volatility, liquidity, correlation), which creates mild ambiguity about whether it can be opted out of.

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 ('Calculate multi-factor risk assessment for cryptocurrencies') and immediately decomposes it into four named factors, which implicitly separates it from the single-factor sibling analyze_volatility. An agent can tell what this produces (a 0-1 score plus recommendations) without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The 'Use Case: Assess position sizing and stop-loss levels' line gives concrete decision contexts, which is more than most tools offer. It stops short of explicit exclusions or naming an alternative (e.g., when to prefer analyze_volatility for a single-factor read), so it lands at 4 rather than 5.

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