PRUVIQ strategy verdicts (read-only)

Get per-strategy backtest stats for one coin

get_coin_strategy_stats

Read-onlyIdempotent

Get per-strategy backtest statistics (trades, win rate, profit factor, total return, exit reasons, data window) for one OKX USDT-SWAP perpetual, e.g. "BTC", "BTCUSDT" or "BTC-USDT-SWAP". Cells below the minimum sample are flagged. Read-only.

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_coin_strategy_stats"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes	Coin symbol: BTC, BTCUSDT, BTC-USDT-SWAP.

Output Schema

Name	Required	Description	Default
`citation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026
- addedOutput schema / properties / citation / properties / source_sha256
```
Added value: +{
+  "pattern": "^[0-9a-f]{64}$",
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
First observedOct 2, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond them: it lists the metric payload and warns that cells below the minimum sample are flagged, which affects how results should be interpreted.

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 purpose and metric list are front-loaded in one efficient sentence, and the trailing 'Read-only.' is clear. It is slightly redundant with the annotation and schema examples but not wasteful.

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 an output schema present, return values need not be explained, and a single required parameter plus rich annotations lower the remaining burden. The description is nearly complete, though it could mention behavior for unsupported symbols or whether the backtest window is fixed.

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?

There is only one parameter and schema description coverage is 100%, so the schema already documents the symbol format with examples. The description repeats the same examples without adding format, normalization, or validation meaning beyond the schema.

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 (per-strategy backtest statistics for one coin) and enumerates the metrics returned. It implicitly distinguishes itself from siblings like get_strategy_verdict and list_strategies by scoping to one symbol, but never names or contrasts those alternatives.

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: an agent can infer this is for pulling backtest stats on a specific coin. There is no explicit when-to-use versus get_strategy_verdict, list_strategies, or get_daily_rankings, and no exclusions or prerequisites.

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

All PRUVIQ strategy verdicts (read-only) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?