Backtrader MCP

Overview Schema Source Related Servers Discussions Admin

Catalog Snapshot

get_catalog_snapshot

Read-only

Read the bundled strategy catalog snapshot to inspect counts, hashes, and provenance, or page through detailed entries with limit and offset.

Instructions

Read the bundled immutable strategy catalog snapshot.

    By default returns only counts, hashes, and provenance (extensions.
    entry_count reports the 1155 records). Set include_entries=true to page
    through entries with limit (1-100) and offset; pagination reports
    total/has_more/truncated. Prefer search_strategy_catalog for queries.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`include_entries`	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?

With readOnlyHint=true, the description adds substantial behavioral context beyond annotations: the snapshot is bundled and immutable, default returns are limited to counts/hashes/provenance, entry_count reports 1155 records, and pagination exposes total/has_more/truncated. No contradictions with the annotations.

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?

The description is concise and front-loaded with the primary purpose, then default behavior, then optional paging, then the alternative. There is minor wasted or malformed text in 'provenance (extensions.' which reads as an incomplete parenthetical, slightly hurting clarity.

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 tool with an output schema, the description covers the essential context: default vs paged behavior, parameter ranges, pagination semantics, and the sibling tool to prefer for queries. Nothing critical is missing for correct invocation.

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?

The schema provides parameter names and defaults but 0% description coverage. The description compensates by explaining include_entries behavior, limit range (1-100), offset paging, and pagination output fields. It could be slightly more explicit about the exact meaning of each parameter, but the core semantics are conveyed.

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 uses a specific verb and resource: 'Read the bundled immutable strategy catalog snapshot.' It clearly describes what the tool returns (counts, hashes, provenance, or paged entries) and differentiates it from sibling search_strategy_catalog by naming that alternative explicitly.

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 on default usage versus paged entry retrieval and explicitly says 'Prefer search_strategy_catalog for queries.' It does not exhaustively enumerate exclusions, but the main alternative and the conditions for choosing it are clearly stated.

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