Skip to main content
Glama
Sign In

ChartAnt

by net.chartant
OverviewDiscussionsAdmin

Candlestick chart

generate_candlestick_chart
Read-onlyIdempotent

Draw a candlestick (OHLC) chart of prices: open, high, low and close for each period. For a simple price trend use generate_line_chart. Returns a hosted PNG link, a share page, alt text and editable PowerPoint/Excel links.

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
dataYesOne row per period: {time, open, high, low, close}.
themeNodefault (light) or dark background.
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

A4.1/5.0
Behavior4/5

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

Annotations already declare this as a safe, read-only, idempotent, closed-world operation, so the baseline is lower. The description adds valuable disclosure beyond annotations: it returns a hosted PNG link, a share page, alt text, and editable PowerPoint/Excel links.

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?

Three compact sentences: purpose first, alternative second, output shape third. There is no filler, though the phrasing is slightly dense with parentheticals and multiple output types in one clause.

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 six parameters, complete schema coverage, and no output schema, the description covers inputs concisely and compensates for the missing output schema by enumerating return artifacts. It does not discuss size limits or data constraints, but those are already in the schema.

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 description coverage is 100%, with each parameter (data rows, theme, title, width, height, brandTheme) already documented in the schema. The description only restates the OHLC row semantics and adds no new constraints or formatting details beyond the schema.

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?

States a specific verb and resource ('Draw a candlestick (OHLC) chart of prices') and defines the required fields (open, high, low, close per period). It explicitly distinguishes itself from generate_line_chart for simple price trends, so an agent can choose between them without opening a 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?

Gives clear routing guidance: use generate_line_chart for a simple price trend. It does not state when this tool is inappropriate (e.g., data lacking OHLC values) or mention other chart alternatives, but the primary selection context is covered.

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