KLinePic MCP Server

Create an annotated trade-review chart

klinepic_create_review_chart

Generate a PNG candlestick chart with buy/sell markers to review past trades from broker fills.

Instructions

Render one PNG candlestick chart with real buy/sell markers. This consumes render quota; preflight first. It does not provide trading signals or investment advice.

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": {
      "request": "<request>"
    },
    "name": "klinepic_create_review_chart"
  }
}

Input Schema

Name	Required	Description	Default
`request`	Yes	KLinePic Agent API request body. Put chart fields under chart.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 13, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Without annotations, the description adds some behavioral context: quota consumption and disclaiming investment advice. But it lacks details on failure modes, timeouts, or output format, leaving gaps.

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?

Three succinct sentences: purpose, usage caveat, and disclaimer. No wasted words, effectively front-loaded.

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?

Given the tool's complexity (single nested param, no output schema), the description covers core purpose and quota usage but omits details on request structure and expected output, leaving an agent to infer.

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 100% with one parameter described. The description adds 'KLinePic Agent API request body. Put chart fields under chart,' which marginally clarifies but doesn't significantly extend schema information.

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 states 'Render one PNG candlestick chart with real buy/sell markers,' which provides a specific verb and resource. It clearly distinguishes from sibling tools like preflight_review_chart and get_capabilities.

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?

The description says 'This consumes render quota; preflight first,' giving explicit usage context and a prerequisite. However, it does not provide explicit when-not-to-use or alternatives to siblings.

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

Deploy Server