Skip to main content
Glama
Sign In

ChartAnt

by net.chartant
OverviewDiscussionsAdmin

US county map

generate_county_map
Read-onlyIdempotent

Draw a map of US counties coloured by a number: all of the US, or the counties of one state. Name counties with their state ("Cook, IL", "Los Angeles County, California") or use 5-digit FIPS codes ("17031"). With 'state' set, bare county names are looked up in that state. For states, use generate_country_map with country 'US'. 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_county_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesOne row per county.
unitNoUnit for the legend, e.g. 'EUR', 'users', '%'.
stateNoOnly this state, e.g. 'TX' or 'Texas'. Leave out for the whole US.
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).
labelsNoWrite each area's name, value or both on the map (default none). Labels that don't fit are left out.
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.9/5.0
Behavior5/5

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

Annotations already establish that this is a safe, idempotent, non-destructive read, so the description's job is to add context — and it does: it discloses the return payload (hosted PNG link, share page, alt text, editable PowerPoint/Excel links) and the edge-case behavior that labels which don't fit are dropped. That is behavior an agent could not infer from the schema or annotations.

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?

Four tight sentences: what it draws, how to identify counties, how 'state' changes resolution, where to go for state maps, and what comes back. The most decision-relevant routing information is front-loaded and no sentence is filler.

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?

For a 9-parameter generation tool with no output schema, the description covers input conventions, the state-vs-country alternative, and the shape of the response, which is everything an agent needs to call it correctly. The remaining limits (max 5000 rows, size bounds, enums) are fully documented 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 coverage is 100%, so the baseline is 3, and the description earns an upgrade by adding real meaning: county identification accepts either "Cook, IL"-style names or 5-digit FIPS ("17031"), and bare names are resolved against 'state'. It does not add anything for the sizing/format/label parameters, which the schema already covers adequately.

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 of US counties coloured by a number") plus its scope (whole US or one state), which immediately separates it from the other map tools. It also names the sibling to use for state-level maps, so an agent can route correctly without opening either schema.

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?

Gives explicit routing: use this for counties, use generate_country_map with country 'US' for states. It also states the conditional behavior of 'state' (bare names are resolved within that state) and restricts brandTheme to "only when the user asks for their theme", which is exactly the kind of when-to-use rule an agent needs.

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