Skip to main content
Glama

TallyForge Quant Signals

Walk-Forward Trend Backtest Summary

walkforward_backtest_summary

Runs a fee-aware walk-forward test of a long-only SMA crossover strategy on up to ~900 days of daily data for a major crypto asset (re-optimized on 180 days, tested on the next 60) and returns out-of-sample return vs buy-and-hold, per-fold results and a pass/fail verdict.

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": "walkforward_backtest_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesCrypto ticker quoted in USD on Coinbase, e.g. BTC, ETH, SOL
fee_bpsNoTrading fee per side in basis points (0-100). Default 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the methodology well: fee-aware, long-only, fixed re-optimize/test window sizes, and the exact return artifacts (out-of-sample vs buy-and-hold, per-fold results, pass/fail verdict). It omits operationally relevant traits — expected runtime for a multi-fold optimization, data source/availability limits, and the criteria behind the pass/fail verdict — so it is informative but not fully transparent.

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?

A single front-loaded sentence with the verb first and no filler; every clause adds substantive information about scope or output. It is dense to the point of being slightly hard to parse in one pass, which keeps it from a 5.

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?

No output schema exists, and the description compensates by enumerating the returned artifacts (out-of-sample return vs buy-and-hold, per-fold results, pass/fail verdict). Combined with full schema coverage, this is nearly sufficient; only cost/runtime expectations and the basis of the verdict remain unstated.

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%, so both parameters are already documented, including the enum of 34 tickers and the 0-100 bps fee range with a default of 10. The description reinforces why fees matter ('fee-aware') and that history is capped at ~900 days, but adds no parameter-level detail the schema lacks; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Runs a fee-aware walk-forward test of a long-only SMA crossover strategy') with concrete scope: up to ~900 days of daily data, 180-day re-optimization, 60-day test windows, and the outputs it produces. The backtest framing makes it unmistakable against the snapshot/matrix siblings without needing to name them.

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?

The strategy-evaluation framing implies when the tool is appropriate (assessing whether an SMA crossover approach holds up out-of-sample on a given asset), but there is no explicit when-to-use, when-not-to-use, or alternative routing guidance. Nothing warns against, for example, using it as a live signal generator rather than a historical evaluation.

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