Skip to main content
Glama
Sign In
KLinePic MCP Server

KLinePic MCP Server

by sher1096
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Check KLinePic API access and quota

klinepic_get_capabilities

Retrieve your API key status, permissions, quota, and supported endpoints for the chart generation service.

Instructions

Check the current Agent API key, permissions, free or paid quota, and supported endpoints.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It honestly discloses that the tool queries current key, permissions, quota, and endpoints. This is a read-only check with no destructive potential, though response format is not described.

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?

Single sentence, front-loaded with 'Check', zero wasted words. Perfectly concise for a parameterless tool.

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?

Low complexity (0 params, no output schema). Description covers what capabilities are checked. Missing details on response format are acceptable for such a simple tool.

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?

No parameters exist; baseline 4 applies. Description doesn't add param info because it's not needed. Schema coverage is 100% implicitly.

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?

Description clearly states verb 'Check' and resource 'KLinePic API' with specific items: API key, permissions, quota, supported endpoints. Distinguishes from sibling tools which focus on chart creation and preflight checks.

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?

Context implies use before chart creation operations to verify access and quota, but no explicit when-not or alternative guidance. Sibling names suggest workflow context (preflight, create).

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

Deploy Server

Other Tools