ChartAnt

World map

generate_world_map

Read-only

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.

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 14, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds the meaningful behavioral fact that unmatched names are listed back in the result, which tells the agent how failures surface rather than being silent. It also notes SVG returns a link to a vector version, though that detail largely duplicates the schema.

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 and encoding, then input format, then the failure note. No restatement of the name or title and no wasted wording.

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?

All 8 parameters are documented in the schema, and the description covers encoding, input format, and the unmatched-name behavior with no output schema to require return documentation. It stops short of saying what the successful return looks like (image vs. link), which is the only leftover gap for an 8-parameter generation 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?

Schema coverage is 100%, so a 3 is the baseline, but the description earns above that by explaining that 'country' accepts common-language names or ISO 3166 codes with examples ('Japan', 'JP', 'JPN') and that the listed-name set is flexible while unmatched entries are reported. That is real semantic meaning beyond the schema's 'One row per country.'

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?

States a specific verb and resource ('Draw a world map') plus the encoding ('colouring countries by a number') with concrete examples of what the number can represent. An agent can tell this produces a choropleth world map and distinguish it from the country/county/ranking map siblings without opening the schema.

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 by the purpose, and the description gives input guidance (country names in any language or ISO codes), but it never says when to prefer this over generate_country_map, generate_ranking_map or a regional map, nor any exclusions. Adequate but leaving the sibling routing 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.

Resources

Need Help?