Skip to main content
Glama
Sign In

ChartAnt

by net.chartant
OverviewDiscussionsAdmin

Map with a top-10 ranking

generate_map_ranking
Read-only

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'.

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.9/5.0
Behavior4/5

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

Annotations already establish that this is a read-only generation tool. The description adds useful behavioral context beyond that: the output is a single image combining a map and bar chart with matching colours, and it explains the readability benefit. It does not cover auth, rate limits, or detailed rendering constraints, but the annotations lower the burden.

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 description is three tight sentences with the core purpose front-loaded. Every sentence adds useful information about the output, readability rationale, and input naming convention without unnecessary 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?

For a moderately complex visualization tool with six fully documented parameters and no output schema, the description provides enough context to understand the generated image and key input convention. It could mention the top-count constraint or broader data limits, but those are available in the schema.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful semantic guidance for the 'name' field by specifying that region names or ISO codes should be used, which goes beyond the schema's length constraint. It does not further explain top, unit, title, or brandTheme, but the schema already documents those.

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 states a specific verb and composite resource: draw a map alongside a bar chart of top places as one image. It clearly distinguishes the output from a map alone by explaining that the bars provide exact numbers, but it does not explicitly name sibling alternatives such as generate_world_map or generate_bar_chart.

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 description implies when to use it by saying it is easier to read than a map alone because the bars give exact numbers. However, it does not explicitly state when to choose this over sibling map or chart tools, nor does it provide exclusions or alternative tool names.

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