Skip to main content
Glama

alpha-sentinel-mcp

calculate_risk_score

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 observed

TDQS

A3.9/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 disclose substantive behavior: the $0.03 per-call cost, the 0-1 output scale, the four-level risk taxonomy, and the factor weighting scheme (40/25/20/15). It omits latency, rate limits, and whether per-factor breakdowns are returned, but the cost and weighting disclosures are the kind of context annotations would normally supply.

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?

Front-loaded with the core purpose, then structured headers for use case, cost, risk levels, and factors. The bold-header formatting adds some visual noise, but every line conveys usable information 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?

With no output schema, the description does the work of explaining returns at a high level (0-1 score, LOW/MEDIUM/HIGH/CRITICAL levels, actionable recommendations). For a two-parameter read-only computation this is nearly sufficient; only the exact shape of the response per symbol and per factor is left unspecified.

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 both parameters are already documented in the schema; baseline 3 applies. The description adds marginal value by naming the analyzed factors, but it lists 'market cap tier' as a factor while the include_factors enum only offers volatility, liquidity, and correlation, creating a small mismatch an agent could trip over.

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 ('Calculate multi-factor risk assessment for cryptocurrencies') and enumerates the exact inputs to the score (volatility, liquidity, market cap tier, BTC correlation) plus the 0-1 output scale. This implicitly separates it from single-factor siblings like analyze_volatility, but no sibling is named or explicitly excluded.

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?

'Use Case: Assess position sizing and stop-loss levels' gives a concrete decision context for when to call it. It offers no when-not guidance and names no alternative for single-factor or non-risk analysis, so the agent must infer boundaries from sibling names.

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.