Skip to main content
Glama
Sign In

amCharts 5

by io.github.amcharts
OverviewDiscussionsAdmin

Search all content

search_all
Read-onlyIdempotent

Search across all amCharts 5 content: skill references, full documentation, and code examples. For broad searches across everything.

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": {
      "query": "<query>"
    },
    "name": "search_all"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query, e.g. 'react integration', 'date axis formatting', 'stacked bar example'. An amcharts.com link (a demo or a docs page) is answered with the call that returns it.
maxResultsNoMaximum results (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Search query, e.g. 'react integration', 'date axis formatting', 'stacked bar example'"New value: +"Search query, e.g. 'react integration', 'date axis formatting', 'stacked bar example'. An amcharts.com link (a demo or a docs page) is answered with the call that returns it."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorldHint=false, so the safety profile is fully covered. The description's only added behavioral value is clarifying what corpus is actually searched, which meaningfully complements openWorldHint=false. No return shape, ranking, or result-volume behavior is disclosed.

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?

Two short sentences with the resource scope front-loaded. The second sentence largely restates the first ('all ... everything'), costing a few words of redundancy, but nothing is buried or padded.

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 two-parameter, non-destructive read tool with rich annotations and a fully documented schema, the definition supplies what is needed to call it correctly. Return format is unstated, but with no output schema and a self-describing query parameter, that is a minor gap.

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% and the schema itself is unusually informative, including the note that amcharts.com links resolve to a returning call. The description adds no parameter guidance beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Search across all amCharts 5 content') and enumerates the three corpora covered: skill references, documentation, and code examples. It implicitly contrasts with the narrower search_docs sibling via 'all' and 'everything', but never names that sibling explicitly.

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?

'For broad searches across everything' gives a usable selection cue against narrower tools, but it is implied rather than spelled out — no sibling is named and no when-not condition is stated. An agent can infer the routing, but must do the work itself.

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