Backtrader MCP

by cloudQuant

Overview Schema Source Related Servers Discussions Admin

Python

Local

Search Strategy Catalog

search_strategy_catalog

Read-only

Search built-in strategy patterns by text and archetype to identify reusable backtesting templates.

Instructions

Search deterministic built-in patterns by text and archetype.

    Returns total/has_more/offset pagination metadata. Empty results carry
    suggestions with the valid archetype list. Unknown archetypes enumerate
    the valid values in the error message.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	No
`offset`	No
`archetype`	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.3/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description reveals useful behavioral details: pagination metadata in responses, suggestions for empty results, and error behavior for unknown archetypes. This materially helps an agent anticipate 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 main sentence front-loads the tool's purpose, and the two follow-up sentences describe response and error behavior. There is no filler or 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?

For a read-only search tool with an output schema and annotations, the description covers invocation mode, pagination, empty results, and invalid input handling. It provides enough context for an agent to select and call the tool correctly.

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 explains that query is text search and archetype filters patterns, and offset is implied by pagination metadata. However, limit/offset semantics and valid archetype values are not explicitly defined, leaving partial coverage.

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?

States a specific verb and resource: search deterministic built-in patterns by text and archetype. It clearly implies a filtered query over the catalog, which is distinct from snapshot/refresh siblings, though it does not explicitly name an alternative.

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 context for when to use the tool: when searching built-in patterns by text or archetype. It does not explicitly exclude alternatives or mention get_catalog_snapshot for full listing, but the search trigger is stated directly.

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