Skip to main content
Glama
Aaditya2502

TradeMCP

by Aaditya2502

trade_list_backtests

Read-onlyIdempotent

Browse and paginate through backtest runs to discover run IDs and summaries. Specify limit and offset to navigate results.

Instructions

List available backtest runs, most useful for discovering run IDs.

Returns a paginated list of run summaries. Pair this with trade_get_backtest to drill into a specific run's full metrics.

Args: params (ListBacktestsInput): Validated input containing: - limit (Optional[int]): Max runs to return, 1-50 (default 10) - offset (Optional[int]): Runs to skip for pagination (default 0) - response_format (ResponseFormat): "markdown" (default) or "json"

Returns: str: Markdown summary, or JSON with this schema: { "total": int, # total runs available "count": int, # runs in this page "offset": int, # current offset "items": [ { "run_id": str, "strategy": str, "symbol": str, "ran_at": str, "total_return_pct": float, "sharpe_ratio": float } ], "has_more": bool, "next_offset": int | null # offset for the next page, if any } On failure: "Error: "

Examples: - "What backtests have I run?" -> default page - "Show me the next 10 backtests" -> offset=10

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. The description adds valuable behavioral context: pagination behavior (limit/offset), response format options (markdown/json), and error format. This goes beyond what annotations provide.

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?

Description is concise and well-structured: one-line purpose, then details, args, returns, and examples. Every sentence adds value, with no redundancy or fluff.

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?

Given the tool's simplicity (3 parameters, output schema provided), the description covers all necessary aspects: purpose, usage guidelines, parameter details, return format, error handling, and examples. It is fully complete for an AI agent to use correctly.

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 descriptions exist for each parameter, but the description adds default values (limit=10, offset=0, response_format='markdown') and explains the output format schema. The 'Args' section re-inforces parameter meaning, and the 'Returns' section details the JSON structure, adding significant value beyond the schema.

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?

The description clearly states 'List available backtest runs, most useful for discovering run IDs' and distinguishes from sibling 'trade_get_backtest' by suggesting pairing. The verb 'list' is specific and the resource 'backtest runs' is well-defined.

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?

The description explicitly says to pair with 'trade_get_backtest' for detailed metrics and gives concrete examples (default page vs offset=10). It tells the agent when to use pagination, though it doesn't explicitly state when not to use this tool vs alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Aaditya2502/trade-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server