Skip to main content
Glama

fr_communes

Look up French municipality data by name, postcode, or INSEE code, returning official identifiers, population, area, department, region, EPCI, SIREN, and center coordinates.

Instructions

French municipalities (INSEE COG) by name, postcode or INSEE code: official name, INSEE code, postcodes, population, area, department, region, EPCI, SIREN, centre coordinates. Costs 0.001 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fr_communes"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoCommune name
inseeNo5-char INSEE code
limitNo1-20
postcodeNo5-digit postcode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the per-call price (0.001 USDC on Base), the x402 payment protocol, and the failure mode when no payment key is present (a 402 challenge). It stops short of describing match semantics (exact vs. partial name matching) or whether results are ranked or truncated.

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, zero filler: the first delivers the resource, keys, and return fields; the second delivers the cost and payment failure mode. Both are front-loaded and an agent can act on them immediately.

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?

There is no output schema, so listing the returned fields is necessary and it is done thoroughly; the payment model is also covered. The remaining gap is ambiguity handling — multiple matches for a name, and how limit interacts with result ordering — which matters for a lookup tool with optional parameters.

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 100%, so each parameter is already documented in the schema, and the description only restates the three search keys without adding format or matching rules. The limit parameter ('1-20') is never mentioned in the description, though the schema covers it.

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 names a specific resource (French municipalities from INSEE COG) and enumerates the lookup keys (name, postcode, INSEE code) plus the returned attributes, so an agent knows exactly what domain this covers. It does not explicitly contrast itself with the nearby fr_address tool, leaving that distinction to inference.

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?

Usage is implied by the lookup keys: use this when you have a commune name, postcode, or INSEE code. There is no explicit statement of when to prefer it over fr_address or other French lookup siblings, and no guidance on what to do when several communes share a name or postcode.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.