Skip to main content
Glama
trading-crew-mcp

trading-crew-mcp

save_candles

Save up to 20,000 candles of a timeframe to a JSON file and return its path so analysis scripts can read exact market data.

Instructions

Save up to 20000 candles of a timeframe to a JSON file and return its path, so analysis scripts can read exact data. Loads the full history if needed (M15 reaches back about 4 months).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "save_candles"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
countNo
resolutionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses that the tool writes a JSON file to disk, returns the path, and may trigger a full-history load ("Loads the full history if needed"), which signals a potentially expensive operation. It omits where the file is written, whether an existing file with the same name is overwritten, and whether the write requires any permissions, all of which matter for a filesystem mutation.

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?

Two sentences, front-loaded with the action and output, then the behavioral caveat about full-history loading. No filler or restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

It correctly covers the return value (a file path) in the absence of an output schema and flags the history-loading behavior, which is meaningful for a three-parameter tool. However, with no annotations and 0% schema coverage, gaps around the "name" parameter, resolution format, and file destination leave an agent with unanswered questions before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 define all three parameters. It explains the count cap (matching the schema maximum of 20000), the timeframe concept, and hints at resolution format via "M15", but the "name" parameter is never addressed and no accepted resolution syntax or default range is given.

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?

The description states a specific verb and resource ("Save ... candles of a timeframe to a JSON file and return its path") and clarifies the output artifact, which separates it from data-returning siblings like get_candles. It never names an alternative tool explicitly, so the differentiation is implied by the file-based output rather than stated.

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

Usage Guidelines3/5

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

Usage is implied by "so analysis scripts can read exact data" and the note that it loads full history when needed, which tells an agent this is the bulk-export route. There is no explicit when-not guidance, no named alternative such as get_candles, and no mention of cost/latency tradeoffs that would steer an agent away for small requests.

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