Skip to main content
Glama
Sign In

ChartAnt

by net.chartant
OverviewDiscussionsAdmin

Pin map

generate_pin_map
Read-onlyIdempotent

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. To count points per region instead of pinning each one use locate_points with map set; to colour whole areas use generate_world_map or generate_country_map. 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_pin_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesOne row per place.
unitNoUnit for the legend, e.g. 'EUR', 'users', '%'.
titleNoTitle shown above the map.
widthNoImage width in pixels (default 960).
formatNopng (default) or svg. SVG returns a link to a vector version of the map.
heightNoImage height in pixels (default 600).
brandThemeNoName 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.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description need not carry the safety profile. It adds useful context beyond annotations: the map auto-zooms to the points and returns a hosted PNG link, share page, alt text, and editable PowerPoint/Excel links. Limits and auth requirements are not covered, but that is a minor gap given the annotation coverage.

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 purpose is front-loaded, followed by value sizing, automatic zoom, alternatives, and return artifacts. Every sentence adds routing or behavioral information, with no redundant wording.

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?

There is no output schema, so the description appropriately names the return artifacts: hosted PNG link, share page, alt text, and editable PowerPoint/Excel links. With full schema coverage and annotations covering safety, an agent has enough information to call this tool correctly.

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 the schema already documents title, width, height, format, unit, brandTheme, and the nested data fields. The description adds meaning mainly for 'value' by saying it sizes the dots, and implies names are labels, but otherwise leaves parameter semantics to the schema. The baseline 3 is appropriate.

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 map with labelled dots at given latitude/longitude anywhere in the world', with examples and the optional value sizing. It is clearly distinguishable from locate_points and the area-map siblings.

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?

Explicitly routes the agent: use locate_points with map set to count points per region instead of pinning each one, and use generate_world_map or generate_country_map to colour whole areas. This gives clear when-to-use and when-to-use-an-alternative guidance.

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

All ChartAnt toolsInspect
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