Skip to main content
Glama

HPSILab Quant Finance

Pre-Trade Risk Scan

get_pretrade_risk_scan

Full pre-trade risk scan JSON for a stock. Pro tool ($0.15/call via x402 for anonymous callers; Credits for signed-in accounts).

`riskDeltas` compares the SPY benchmark (`beforeValue`) with this stock on
its own (`afterValue`). Neither side is a portfolio, so it is not a
before/after of the caller's holdings; `exposure` and `correlation` are
the parts that use the holdings (see `methodology.riskDeltas`).

Signed-in hpsilab users (including Free, on its trial Credits) spend
Credits from their balance at this tool's catalog price — each tool is
priced differently; see GET /api/credits/catalog.
Anonymous / tokenless agents pay per call via x402 (USDC on Base) when
payments are enabled — send the x402 payment in the request _meta.

Args:
    symbol: Stock symbol, e.g. "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": {
      "symbol": "<symbol>"
    },
    "name": "get_pretrade_risk_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesStock ticker symbol, e.g. AAPL.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / symbol / description
      Added value: +"Stock ticker symbol, e.g. AAPL."
    • addedInput schema / properties / symbol / examples
      Added value: +[
      +  "AAPL"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnly/openWorld/idempotent/destructive flags, so the description carries real load: it discloses per-call cost ($0.15 via x402 USDC on Base), that signed-in users spend Credits, that payment goes in request _meta, and that the endpoint is 'Pro' tier. It also preempts a serious misreading of riskDeltas by clarifying that beforeValue is the SPY benchmark, not the caller's portfolio. Data freshness and rate limits remain unstated, keeping it below 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the riskDeltas clarification earns its space, but the Args block duplicates the schema verbatim and the pricing paragraph spends a sentence on catalog navigation ('each tool is priced differently; see GET /api/credits/catalog'). The prose is also line-broken mid-sentence, which hurts scannability.

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?

An output schema exists, so return values need not be itemized, and the description still explains the key output field semantics (riskDeltas vs. exposure/correlation). Payment and auth paths are fully covered. What is missing for a paid, compute-heavy scan is any note on data freshness, latency, or failure/refund behavior.

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% and there is only one parameter, so the schema already documents `symbol` fully. The description's 'symbol: Stock symbol, e.g. "NVDA"' merely restates what the schema's own example and description provide, adding no syntax, normalization, or lookup behavior.

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?

Opens with a specific verb+resource: 'Full pre-trade risk scan JSON for a stock.' The resource is distinctive enough that it is not confusable with the sibling tools. It stops short of explicitly contrasting with siblings such as analyze_stock or get_monte_carlo, so it lands at 4 rather than 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?

Usage is only implied by the name ('pre-trade') and by the pricing/auth block explaining who can call it and how to pay. There is no explicit statement of when to pick this scan over analyze_stock, get_iv_radar, or get_monte_carlo, and no exclusions or prerequisites beyond payment.

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.