Skip to main content
Glama

PolySignals.net

Live backtest

get_results
Read-only

What following the calls would have returned, trading the coin against USD on Coinbase with fees, next to buy and hold: net and gross return, round trips, win rate, drawdown and the current position. Without a coin: one strategy (default: the daily regime) for every coin; with a coin: all eight strategies.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinNoCoin ticker or name as on the site, for example BTC, ETH or SOL
strategyNoDefault regime; ignored when a coin is given

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds substantive context beyond them by disclosing the simulation basis (fees, Coinbase USD, buy-and-hold benchmark) and the exact metric set produced. It does not discuss cost, latency, or time-range bounds, which keeps it short of a 5.

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?

Two sentences, both dense with information and no filler; the metric list precedes the coin/strategy branching. The opening relative clause ('What following the calls would have returned') is the one piece of awkward, back-loaded phrasing that could be front-loaded as 'Backtest results'.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 carries the return-value burden and does so fully by enumerating the metrics, the fee/venue assumptions, and the benchmark. All optional parameters' effects are explained, so an agent can call it correctly with or without arguments.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: the cross-product semantics (one strategy across all coins vs. all strategies for one coin) and the fact that the default strategy is the daily regime. The 'ignored when a coin is given' precedence is repeated from the schema but reinforces a genuinely easy-to-miss interaction.

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?

The description states the resource concretely: a backtest of 'what following the calls would have returned', traded against USD on Coinbase with fees versus buy-and-hold, and enumerates the returned metrics (net/gross return, round trips, win rate, drawdown, current position). It is distinguishable from the live-signal siblings by the explicit 'would have returned' framing, though it never names those siblings directly and the opening clause is grammatically indirect.

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?

It gives clear invocation context: no coin returns one strategy (default regime) for every coin, while supplying a coin returns all eight strategies for that coin. That is actionable scoping guidance, but there is no exclusion or routing advice telling the agent when to prefer this over get_coin_signal or get_regime instead.

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.

Resources