ChartAnt

World map

generate_world_map

Read-onlyIdempotent

Draw a world map colouring countries by a number (sales, population, users, visitors by country). Use country names in any common language or ISO 3166 codes (e.g. 'Japan', 'JP', 'JPN'); unmatched names are listed in the result with 'Did you mean' hints. For regions inside one country use generate_country_map; to show exact numbers beside the map use generate_map_ranking. 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_world_map"
  }
}

Input Schema

Name	Required	Description
`data`	Yes	One row per country.
`unit`	No	Unit for the legend, e.g. 'EUR', 'users', '%'.
`title`	No	Title shown above the map.
`width`	No	Image width in pixels (default 960).
`format`	No	png (default) or svg. SVG returns a link to a vector version of the map.
`height`	No	Image height in pixels (default 540).
`labels`	No	Write each area's name, value or both on the map (default none). Labels that don't fit are left out.
`brandTheme`	No	Name 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.

First observedNov 15, 2026

TDQS

A4.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 closed-world, so the safety profile is covered. The description earns credit for two things annotations cannot carry: fuzzy country-name matching with "Did you mean" hints in the result, and the full return bundle (PNG link, share page, alt text, editable PowerPoint/Excel links). It does not discuss input limits such as the 5000-row cap or what happens on partial matches beyond listing them.

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 sentences, front-loaded with the core action, then input flexibility, then routing, then outputs. Every clause carries information an agent needs; no filler or restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter, no-output-schema tool, the description covers the input semantics, sibling routing, and the shape of the return value, which is exactly what the absent output schema would otherwise need to supply. Nothing material is missing for correct invocation.

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?

With 100% schema coverage the baseline is 3, but the description adds real meaning about the `country` field the schema does not: any common language name or ISO 3166 alpha-2/alpha-3 code, with examples. It also implicitly clarifies that `value` is the number driving the colour scale. It does not explain the colour-scale/bucketing behaviour or the `labels` overflow rule, though the schema covers the latter.

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?

Opens with a concrete verb and resource: "Draw a world map colouring countries by a number," and immediately grounds it with use-case examples (sales, population, users, visitors). It names two sibling tools it is not, so an agent can route 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing rules: use generate_country_map "for regions inside one country" and generate_map_ranking "to show exact numbers beside the map." Both the condition and the alternative are stated, leaving nothing to inference.

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

All ChartAnt tools Inspect

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.