Skip to main content
Glama
roman-zaglauer

OctoBot MCP Server

by roman-zaglauer
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Local

list_data_files

Show available historical data files on your OctoBot instance with exchange, symbols, time frames, and dates to help select datasets for backtests or cleanup.

Instructions

List every historical data file already present on the OctoBot instance.

Tier-B (ADR-0008): scrapes the bare GET /data_collector page -- see this module's docstring/_parse_data_collector_html for the verified DOM shape and fail-loud assumptions. Idempotent, read-only, not confirm-gated.

Output: {"files": [{"file": str, "exchange": str, "symbols": [str], "time_frames": [str], "is_full": bool, "start_date": str|null, "end_date": str|null, "date": str|null, "candles_length": int|null}]}. file is the authoritative identifier to pass to delete_data_file. An empty files list is a legitimate result (no data files exist yet) -- distinct from DataFileScrapeContractBrokenError, which means the scrape itself is broken, never silently returned as an empty/partial list (NFR-13).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description fully carries behavioral disclosure. It explicitly states idempotency, read-only behavior, lack of confirmation gating, the scraping mechanism, fail-loud assumptions, and the distinction between an empty list and a scrape contract break. This is thorough and actionable.

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 adds necessary implementation and behavioral details in a compact, structured format. The output schema is inline and each sentence provides actionable information without 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 zero-parameter read-only tool, the description is complete: it specifies the resource, output shape, error semantics, and relationship to delete_data_file. The agent has everything needed to understand when to call it and how to interpret the result.

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 tool has zero input parameters, so the baseline of 4 applies. The description compensates further by documenting the full output structure and the meaning of the `file` field, which helps the agent interpret the result even though no output schema exists.

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 states a specific verb and resource: list every historical data file present on the OctoBot instance. It clearly differentiates the tool from siblings like delete_data_file, import_data_file, and start_data_collection by emphasizing enumeration of existing files.

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 implies when to use the tool by stating that the returned `file` value is the authoritative identifier to pass to `delete_data_file`, which routes an agent toward file-management workflows. It also notes the tool is not confirm-gated. However, it does not explicitly contrast with other listing or data-collection tools.

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