@munispot/mcp

search_municipalities

Search and filter U.S. municipalities by name, state, sector, MuniScore range, and population to identify local governments that match specific criteria.

Instructions

Search and filter 20,000+ US municipalities by name, state, sector, MuniScore range, and population.

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": "search_municipalities"
  }
}

Input Schema

Name	Required	Description
`q`	No	Search term to match against municipality name
`page`	No	Page number
`state`	No	Two-letter state code
`sector`	No	Municipality type
`per_page`	No	Results per page (max 25)
`max_score`	No	Maximum MuniScore (0-100)
`min_score`	No	Minimum MuniScore (0-100)
`fiscal_year`	No	Fiscal year (default: 2024)
`max_population`	No	Maximum population
`min_population`	No	Minimum population

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Oct 27, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses dataset scale (20,000+ municipalities), which is genuinely useful, but says nothing about pagination limits, default sort order, result caps, or whether all parameters are optional — all of which matter for a 10-parameter unannotated search.

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?

A single front-loaded sentence with no filler; the resource and the filterable dimensions lead immediately. Nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter, zero-required search tool with no annotations and no output schema, the description covers what can be searched but not how results are shaped or limited (pagination defaults, max 25 per page, sort order, what a result record contains). Adequate to select the tool, thin for invoking it confidently.

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 description coverage is 100%, so the baseline is 3. The description corroborates the filterable facets (name, state, sector, MuniScore range, population) that map to the schema's q, state, sector, min/max_score, and min/max_population, but omits any mention of pagination or the fiscal_year default, adding no syntax or format meaning beyond the schema.

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 verb ('Search and filter'), a concrete resource ('20,000+ US municipalities'), and enumerates the facet dimensions available. It implicitly contrasts with get_municipality by emphasizing breadth ('20,000+'), but no sibling is named explicitly, which keeps it short of a 5.

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

Usage Guidelines2/5

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

The sentence describes capability only; there is no 'use this when' framing, no mention of when to prefer get_municipality for a single lookup, and no note about when compare_municipalities is the better route. An agent must infer the discovery use case from the facet list alone.

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

Deploy Server