tw-market-data

List backtests

list_backtests

Read-onlyIdempotent

Browse an INDEX of your past backtest runs — ids and headline metrics only, no re-execution.

    Use when you want to find a run whose id you have forgotten. It never re-computes anything:
    `run_backtest` executes a new one, `get_backtest` opens a single record in full, and
    `replay_backtest` re-derives one to check reproducibility. This is the catalogue, not any of
    those three. Args: optional strategy_id filter, limit.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`strategy_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hint`	No
`runs`	No
`count`	No
`reason`	No
`blocked`	No
`not_investment_advice`	No

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable context beyond annotations by explicitly stating 'never re-computes anything' and describing the output as an index of ids and headline metrics. This reinforces and enriches the safety profile without contradicting it.

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?

The description is front-loaded with the core purpose, then usage guidance and alternatives, and ends with a compact args line. Every sentence adds distinct value with no redundancy.

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 no required parameters, a simple index operation, and a true output schema, the description covers everything an agent needs: what the tool returns, when to use it, what it never does, and how it differs from related tools. No significant gap remains.

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 0%, so the description must compensate. It names the two parameters ('optional strategy_id filter, limit') but does not elaborate on their semantics — e.g., that limit caps the result count or that strategy_id narrows to a specific strategy's runs. Some meaning is inferable from names and defaults, but the description does not fully carry the burden.

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?

Description states a specific verb ('Browse an INDEX') and resource ('past backtest runs'), and clarifies scope: 'ids and headline metrics only, no re-execution.' It clearly distinguishes itself from siblings by saying 'This is the catalogue, not any of those three.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it ('Use when you want to find a run whose id you have forgotten') and names three alternatives with their distinct purposes: run_backtest, get_backtest, and replay_backtest. This leaves no ambiguity about when to select this tool.

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

All tw-market-data tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

The tools are largely distinct: querying, searching, backtesting, risk reads, alerts, memory, and audit functions each have clear homes. A few adjacent pairs (risk_read vs risk_assess, company_health_check vs positioning_read) could be confused, but the descriptions draw explicit boundaries.

Naming Consistency3/5

There are strong consistent clusters like list_*, get_*, run_*, and memory_*, but the *_read suffix alternates with noun-first names like company_health_check, and bare-verb tools like ask, calendar, chart, and screen break the pattern. The naming is readable but not uniform.

Tool Count2/5

Forty tools is well past the 25+ threshold and makes the surface heavy for an agent to navigate, even though the breadth reflects a genuinely wide platform. Several clusters could plausibly be consolidated without losing capability.

Completeness4/5

The tool surface covers the main lifecycle well: discovery, point-in-time querying, filings search and full text, backtesting, research, risk assessment, alerts, memory, approvals, and provenance verification. Minor gaps exist—no strategy management tools, no memory deletion, no bulk export—but agents can work around them.

Resources

Need Help?