Skip to main content
Glama

FinanceQuery

Risk Analytics

get_risk
Read-onlyIdempotent

Get risk analytics: VaR (95/99%), Sharpe/Sortino/Calmar ratios, beta, and maximum drawdown for a symbol.

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

Input Schema

NameRequiredDescriptionDefault
rangeYesTime range: 1y|2y|5y (default: 1y)
fieldsNoComma-separated list of GraphQL field names to include; omitted = curated default set
symbolYesStock ticker symbol
intervalYesCandle interval: 1d|1wk (default: 1d)
benchmarkNoBenchmark symbol for beta calculation (e.g., "SPY")

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?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered without the description. The description adds the computed metric set but says nothing about data source, computation window, cost/latency, or what happens when benchmark is omitted for beta — with annotations carrying the load, that is adequate rather than rich.

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?

A single front-loaded sentence with the resource named first and the returned metrics enumerated; every clause carries information and there is 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, listing the returned metrics is genuinely necessary and is done well. Minor gaps remain around required parameters and default behavior, but the schema documents those, so the definition is sufficient for correct invocation.

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%, including descriptions for range, interval, symbol, benchmark, and fields, so the baseline is 3. The description only confirms that results are computed for a single symbol; it adds no interpretation of interval, range, or the fields projection beyond what the schema states.

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 ('Get') and resource ('risk analytics') and enumerates the exact metrics returned (VaR 95/99%, Sharpe/Sortino/Calmar, beta, max drawdown), so the agent knows precisely what it gets. It does not, however, differentiate itself from the closely named sibling get_risk_factors, leaving that distinction to inference.

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 statement of when to use this tool versus alternatives such as get_risk_factors or get_indicators, and no prerequisites or exclusions. Usage is only implied by the metric list.

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.