Skip to main content
Glama
Sign In

amCharts 5

by io.github.amcharts
OverviewDiscussionsAdmin

Get quick-start template

get_quick_start
Read-onlyIdempotent

Get a quick-start template for a specific chart type — a minimal working example ready to customize.

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": {
      "chartType": "<chartType>"
    },
    "name": "get_quick_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format: 'html' for a full HTML page with CDN scripts, 'esm' for ES module importshtml
chartTypeYesChart type, e.g. 'pie', 'line', 'bar', 'map', 'sankey', 'treemap'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive behavior, and a closed-world scope, so the safety profile is covered. The description adds that the returned content is a minimal working example ready to customize, which is helpful context, but it does not elaborate on return shape or format beyond what the schema provides.

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?

The description is a single, front-loaded sentence with no wasted words. It communicates the core purpose and output nature efficiently.

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 simple read-only retrieval tool with two well-documented parameters and clear annotations, the description provides enough context to call it correctly. It could say slightly more about the returned template, but no output schema exists and the description's 'minimal working example' phrasing covers the essential return semantics.

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%, so both parameters are already documented in the schema. The description reinforces that the template is for a specific chart type but adds no parameter details beyond the schema, which is appropriate for the baseline score.

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 states a specific verb and resource: get a quick-start template for a specific chart type. It also clarifies the output nature as a minimal working example ready to customize. It does not explicitly distinguish this from the sibling get_example or get_example-like tools, so it falls short of the top score.

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 implied: use this when you need a quick-start template for a chart type. There is no explicit guidance on when to prefer this over get_example, get_chart_reference, or other sibling retrieval tools, nor are exclusions or alternatives named.

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

All amCharts 5 toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources