Skip to main content
Glama
trading-crew-mcp

trading-crew-mcp

get_candles

Fetches up to 500 recent price candles as a compact oldest-first table with Unix timestamps, optionally reading a specified timeframe and restoring the chart afterward.

Instructions

Last N candles (up to 500) as a compact table {fields, rows}, oldest first, with unix times. For more than 500, use save_candles. Pass resolution (e.g. 60, 240, D) to read another timeframe; the chart is switched and then restored.

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": "get_candles"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
resolutionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does well: it discloses a real side effect ('the chart is switched and then restored'), the return shape, row ordering, and time format. It omits defaults for optional parameters and any latency or rate-limit notes, which keeps it short of a 5.

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 purpose and return shape, then the alternative, then the resolution caveat. Every clause contributes information; there is no repetition or filler.

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?

For a two-parameter read tool with no output schema, the description covers the return format and the side effects adequately. The remaining gap is default behavior: both parameters are optional, yet the description never says what count or resolution is used when omitted.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must supply all meaning, and it does: 'count' means the last N candles bounded at 500, and 'resolution' is the timeframe with concrete example values (60, 240, D) plus the caveat that reading another timeframe temporarily switches the chart. No parameter is left opaque.

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 names a specific resource (candles) with an explicit scope ('last N'), states the return format ({fields, rows}), ordering ('oldest first'), and time encoding ('unix times'). It also distinguishes itself from save_candles by the count threshold, so an agent can identify it without opening the schema.

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?

It gives an explicit alternative with a condition: 'For more than 500, use save_candles.' That covers the main routing decision. It does not address when an agent might prefer get_quote or screenshot instead, but those are outside its stated purpose.

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