Skip to main content
Glama
Sign In

ChartAnt

by net.chartant
OverviewDiscussionsAdmin

Find the region of each point

locate_points
Read-onlyIdempotent

For each latitude/longitude, find the country, its state/province/region (ISO 3166-2) and, in the US, the county (FIPS). Works offline. With map set, also draws a map of how many points fall in each area (regions of the main country, US counties, or countries). Returns one line per point (country › region › county); to pin each point on a map instead use generate_pin_map.

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": {
      "points": "<points>"
    },
    "name": "locate_points"
  }
}

Input Schema

NameRequiredDescriptionDefault
mapNoAlso draw a map of counts per area: auto picks the finest level that fits; leave out for text only.
titleNoTitle of the map (only with map).
pointsYesThe points, each with latitude, longitude and an optional name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorldHint=false, and the description reinforces this with "Works offline," which is genuinely useful context for a lookup tool. It also discloses the side effect that a map is rendered only when map is set, plus the one-line-per-point return format. It does not say what happens for points that match no land area or how resolution/accuracy is determined, which keeps it at 4.

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?

Dense and front-loaded: capability first, then the offline trait, then the map option, then the return format and the sibling pointer. Every sentence carries information and nothing is repeated from the schema verbatim.

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 3 parameters, full schema documentation, and rich annotations, the definition covers what an agent needs: purpose, map behavior, output format, and the alternative tool. Gaps are limited to edge-case behavior (unmatched or ocean points, performance for large point sets).

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 baseline is 3, but the description adds meaning the schema lacks: it maps the map levels to their content ("regions of the main country, US counties, or countries") and states the return ordering (country › region › county). Minor added value, not full compensation-level detail.

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 ("For each latitude/longitude, find the country, its state/province/region (ISO 3166-2) and, in the US, the county (FIPS)"), names the exact output shape, and explicitly separates itself from generate_pin_map. An agent can distinguish this from the chart/map siblings without opening any schema.

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?

Gives the condition that changes behavior ("With map set, also draws a map..."; "leave out for text only") and routes the agent to generate_pin_map when the goal is plotting points rather than geocoding them. No explicit when-not-to-use guidance beyond that alternative, so it falls short of full 5.

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