Skip to main content
Glama
Sign In

ChartAnt

by net.chartant
OverviewDiscussionsAdmin

Candlestick chart

generate_candlestick_chart
Read-only

Draw a candlestick (OHLC) chart of prices: open, high, low and close for each period. Returns an image link.

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": {
      "data": "<data>"
    },
    "name": "generate_candlestick_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
themeNo
titleNoTitle shown above the chart.
widthNoImage width in pixels (default 720).
heightNoImage height in pixels (default 480).
brandThemeNoName of a brand theme saved on the user's account (their colours and footer), only when the user asks for their theme. Or "colorblind" for colours that people with colour-vision deficiency can tell apart (anyone can use it).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the safety profile is already covered. The description adds genuinely new behavioral information that no output schema provides: the tool returns an image link, which tells the agent what to expect back. It stops short of saying whether the image is persisted, shareable, or how large or long-lived the link is.

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 tight sentences: the chart type and required data come first, and the return value follows. Nothing is redundant or buried.

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 read-only chart renderer with no output schema, the description covers what it does, what it needs, and what it returns. Small gaps remain around the time field's accepted formats and the optional styling parameters, but the schema carries most of the constraint burden and nothing critical is missing for a correct call.

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

Parameters3/5

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

Schema coverage is 67% and the description's mention of open/high/low/close per period merely restates the required fields already enumerated in the schema. The optional parameters (theme, title, width, height, brandTheme) are left entirely to the schema, and the ambiguous 'time' field (string or number, no description) gets no clarification in the description.

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 ('Draw') and resource ('candlestick (OHLC) chart of prices') and spells out the four required series (open, high, low, close). That is enough for an agent to distinguish it from the other generate_*_chart siblings by chart type, though it never explicitly contrasts with alternatives like line or bar charts.

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 only implied by the chart-type name: pick this when you have OHLC data per period. There is no statement of when to prefer candlestick over another chart sibling, no prerequisites, and no note on data ordering or limitations such as the 5000-point cap.

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

All ChartAnt toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources