@munispot/mcp

get_municipality

Retrieve a detailed profile for a single U.S. municipality by EIN, including financial, budget, debt, economic, and demographic data for a chosen fiscal year.

Instructions

Get detailed profile for a single municipality by EIN.

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": {
      "ein": "<ein>"
    },
    "name": "get_municipality"
  }
}

Input Schema

Name	Required	Description	Default
`ein`	Yes	Employer Identification Number
`fiscal_year`	No	Fiscal year

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Oct 27, 2026

TDQS

B3.2/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. 'Get' implies a read operation, but the description does not explicitly confirm read-only behavior, explain what happens when the EIN is not found, describe how fiscal_year changes the result, or state any permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no wasted words. It is appropriately sized for a simple retrieval tool, though its brevity leaves important behavioral details unstated.

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?

The tool is low complexity with only two parameters and no output schema. The description still leaves gaps: it does not say what fields the 'detailed profile' contains or how the optional fiscal_year parameter affects the profile. These omissions make it minimally adequate rather than complete.

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 both the EIN and fiscal_year parameters are already documented in the schema. The description adds only the lookup key ('by EIN') and does not clarify the optional fiscal_year parameter, so it meets but does not exceed the baseline.

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 clearly states a specific verb and resource: 'Get detailed profile for a single municipality.' The lookup key, EIN, is included, and 'single' implicitly distinguishes it from search_municipalities. It does not explicitly name sibling alternatives, so it falls 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 Guidelines3/5

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

The phrase 'by EIN' implies this tool is used when the caller already knows the municipality's EIN, rather than searching. However, there is no explicit when-to-use guidance, no when-not-to-use conditions, and no mention of compare_municipalities or get_financials as alternatives.

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

Deploy Server