Skip to main content
Glama
Sign In

ChartAnt

by net.chartant
OverviewDiscussionsAdmin

Map with a top-10 ranking

generate_map_ranking
Read-onlyIdempotent

Draw a map (regions of one country, or countries of the world) next to a bar chart of the top places, in matching colours, as one image. Easier to read than a map alone: the bars give the exact numbers. Use region names or ISO codes as 'name'. 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_map_ranking"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoHow many places the bar chart ranks (default 10).
dataYesOne row per region or country.
unitNoUnit for the legend, e.g. 'EUR', 'users', '%'.
titleNoTitle shown above the map.
countryNoFor regions of one country, e.g. 'DE'. Leave out for a world map of countries.
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

A3.8/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description's real added value is disclosing the return payload: hosted PNG link, share page, alt text and editable PowerPoint/Excel links, which matters since there is no output schema. It says nothing about generation limits or cost/latency, so it clears the annotation-adjusted bar without being rich.

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 visual output, then the value proposition, then the input convention and returns. No sentence is redundant and nothing is buried.

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?

With 100% schema coverage and no output schema, the definition covers both the input convention and the return artefacts, which is the main gap for a generation tool. It stops short of mentioning practical bounds (e.g. the 20-place cap on 'top' or large data handling), leaving that entirely to the schema.

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 six parameters are already documented including the brandTheme and country behaviour. The description adds marginal value by telling the agent what to pass as 'name' (region names or ISO codes), but says nothing extra about 'top', 'unit' or 'data' beyond the schema.

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 plus the composite output: a map of regions/countries placed next to a top-places bar chart in matching colours as one image. That framing cleanly distinguishes it from generate_country_map, generate_world_map and generate_bar_chart, which produce only one of the two views.

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?

It gives a rationale for choosing this over a map alone ('the bars give the exact numbers') and a formatting rule ('Use region names or ISO codes as name'), but never states when not to use it or names an alternative such as a plain bar chart for rank-only data. Usage is implied rather than explicit.

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