ChartAnt

Pin map

generate_pin_map

Read-only

Draw a map with labelled dots at given latitude/longitude anywhere in the world (offices, stores, customers, events). Optional 'value' sizes the dots. The map zooms to the points automatically.

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_pin_map"
  }
}

Input Schema

Name	Required	Description
`data`	Yes	One row per place.
`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 600).
`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

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description contributes genuinely non-obvious behavior in 'The map zooms to the points automatically', but says nothing about the return value (image vs. link, despite there being no output schema) or limits such as the 5000-point cap.

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 short sentences with the core capability front-loaded, followed by the two behavioral facts an agent could not guess (value sizing, auto-zoom). No padding or repetition of the title.

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

Completeness3/5

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

For a tool with seven parameters and no output schema, the description should say what the caller receives (an image, a URL, rendered markdown). It also omits practical constraints like the 5000-point cap and the 'brandTheme only when the user asks for their theme' caution that lives only in the schema. It is adequate but leaves real gaps.

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 all seven parameters are already documented in the structured schema. The one addition, 'Optional value sizes the dots', clarifies the meaning of value beyond its schema text ('minimum: 0'), but the description gives no guidance on unit/legend pairing or brandTheme selection beyond what the schema already says; 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?

The description names a specific verb and resource: 'Draw a map with labelled dots at given latitude/longitude', and the parenthetical examples (offices, stores, customers, events) make the intended data shape concrete. It separates itself reasonably from the country/county/world map siblings by emphasising arbitrary lat/lon points, though it never names an alternative outright.

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?

The use cases ('offices, stores, customers, events') imply when a pin map is the right choice, but there is no explicit when-to-use or when-not statement and no pointer to generate_country_map or generate_world_map for aggregated geography. Guidance is inferable but not stated.

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?