Skip to main content
Glama
Sign In

ChartAnt

by net.chartant
OverviewDiscussionsAdmin

Clean up place names

match_places
Read-only

Turn messy place names into standard names and codes: countries (ISO 3166 codes), the states/provinces/regions of one country (ISO 3166-2 codes) or US counties (FIPS codes). Understands other languages, abbreviations and typos ("Bayern", "BY", "Bavarai" → Bavaria, DE-BY). Use it to clean a column of locations before a map, a join or a report.

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": {
      "names": "<names>"
    },
    "name": "match_places"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNocountry (default without 'country'), region (needs 'country') or county (US).
namesYes
stateNoFor US counties: limit to one state, e.g. 'TX'.
countryNoFor regions: the country, e.g. 'DE' or 'Germany'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's job is to add context — and it does: it discloses that the tool tolerates other languages, abbreviations and typos, and that the return is standardized names plus codes. It omits how unmatched or ambiguous names are reported, which matters for a no-output-schema tool.

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?

Two sentences, front-loaded with the transformation and the code standards, then a parenthetical worked example, then the use case. No filler, and the example earns its space by demonstrating the tolerance for typos and abbreviations.

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 no output schema, the description usefully states what comes back (standard names and codes), and it covers the three normalization levels. It stops short of describing unmatched-name handling or error behavior for a batch of up to 2000 names, which is the main remaining gap.

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 coverage is 75% and the schema itself documents the country/region/county dependency and the state limit for US counties. The description restates that regions are 'of one country' and counties are US-linked, which mildly reinforces the level→country/state coupling but adds no new syntax, format or default information 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?

The description gives a specific verb (turn into standard names and codes) plus the exact resource set (countries, regions, US counties) and names the standards involved (ISO 3166, ISO 3166-2, FIPS). It is clearly a normalization utility, distinguishable from the chart/map generators among its siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states a concrete usage condition: clean a column of locations before a map, a join or a report. That places it clearly upstream of the generate_*_map siblings, but it gives no explicit exclusions or stated prerequisites (e.g., what to do with unmatched input).

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