Skip to main content
Glama

chart_image

Read-onlyIdempotent

The deck's own chart plate for one market, timeframe and window, rendered server-side from the same geometry the screen uses (bars, indicators, the envelope cone when its calibration permits) as a PNG you can look at, together with the chart_state JSON for the same window. The picture is for shape; the numbers are in the JSON — quote those, never read them off the image. Past windows only; at most 600 bars.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "market": "<market>",
      "tf": "<tf>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "chart_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
tfYestimeframe
toYeswindow end, ISO-8601 UTC, in the past
fromYeswindow start, ISO-8601 UTC
marketYesthe market
indicatorsNoindicator ids to draw; defaults to ema20 and envelope

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / tf / enum
      Previous value: -[
      -  "15s",
      -  "1m",
      -  "5m",
      -  "15m",
      -  "1h",
      -  "4h",
      -  "1d"
      -]New value: +[
      +  "1s",
      +  "15s",
      +  "1m",
      +  "5m",
      +  "15m",
      +  "1h",
      +  "4h",
      +  "1d"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / tf / enum
      Previous value: -[
      -  "15s",
      -  "1m",
      -  "5m",
      -  "1h"
      -]New value: +[
      +  "15s",
      +  "1m",
      +  "5m",
      +  "15m",
      +  "1h",
      +  "4h",
      +  "1d"
      +]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the bar is lower, and the description still provides real delta: server-side rendering from the same geometry as the screen, the envelope cone only appearing when its calibration permits, dual PNG plus JSON output, past windows only, and a 600-bar cap. Nothing about authentication tiers or rate limits is covered. It also avoids contradicting any annotation.

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 core purpose and the PNG-versus-JSON division of labour are front-loaded in the first sentence, and the two constraints are appended as short trailing clauses. The sentences are long and dense, but nothing is redundant or filler. Slight readability cost from the nested parenthetical.

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?

With no output schema, the description carries the burden of explaining returns, and it does: a PNG for shape plus chart_state JSON for the numbers, with an explicit instruction to quote numbers from the JSON. Constraints are also covered. The remaining gap is mechanical: it does not say how the image is delivered (inline/base64 vs. reference) or how large a response to expect.

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?

Schema description coverage is 100%, so the baseline is 3 and enum-constrained fields (tf, market) are already fully documented. The description adds genuine meaning beyond the schema: the 600-bar cap constrains how wide a from/to window may be, and 'when its calibration permits' explains why the envelope indicator may be missing from a rendering. This is a moderate but real uplift over the schema.

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 names a specific verb and resource: rendering a chart plate (PNG plus chart_state JSON) for one market, timeframe and window, server-side from the same geometry as the screen. It is far more than a restatement of the name, and it implicitly differentiates itself from the `chart_state` sibling by calling out the extra JSON. It stops short of explicitly naming when to prefer a sibling, so not a clean 5.

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?

It does state the operating envelope ('Past windows only; at most 600 bars'), which the agent needs in order to call the tool validly, and it prescribes how to use the output ('the numbers are in the JSON — quote those, never read them off the image'). However, it never names an alternative such as `chart_state`, `image` or `tape` and the condition that would select them. Usage is therefore implied rather than routed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources