Backtrader MCP

Overview Schema Source Related Servers Discussions Admin

List Jobs

list_jobs

Read-only

List durable backtest jobs newest-first with optional state filtering and pagination metadata, advancing pages via offset.

Instructions

List durable jobs newest-first with pagination metadata.

    Filter by a job state or the pseudo-state "active" (QUEUED/RUNNING/
    CANCEL_REQUESTED). Unknown states enumerate the valid values. Advance
    through pages with offset while has_more is true.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`state`	No
`offset`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 20, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses non-obvious behaviors: the 'active' pseudo-state expands to QUEUED/RUNNING/CANCEL_REQUESTED, unknown states cause enumeration of valid values, and pagination advances with offset while has_more is true. This gives an agent accurate expectations for edge cases.

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 compact and front-loaded, with the core purpose in the first sentence and each subsequent sentence adding a specific, non-redundant usage detail. No filler or repetition exists.

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?

The description is complete for a read-only list tool with an existing output schema: it covers filtering, state semantics, and the pagination loop. The only minor gap is explicit default-limit behavior, but the schema provides the default, so the information is accessible.

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?

With 0% schema description coverage, the description compensates well for state (pseudo-state semantics, unknown-state behavior) and offset (page-advance condition). Limit is not explicitly described, but its name and schema default convey its role; overall, parameter meaning is significantly enriched.

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 opens with a specific verb and resource ('List durable jobs') plus an explicit ordering ('newest-first'), immediately distinguishing it from sibling tools that operate on strategy runs, drafts, and datasets. No ambiguity remains about what this tool does.

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 gives clear operational context: how to filter by state, what the 'active' pseudo-state means, how to handle unknown states, and how to paginate using offset and has_more. It does not name alternative tools, but no sibling has an overlapping purpose, so explicit exclusions are unnecessary.

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