@munispot/mcp

get_economy

Retrieve economic and demographic data for U.S. municipalities using EIN, CBSA code, or state FIPS to analyze local profiles.

Instructions

Get economic and demographic data by municipality EIN, CBSA code, or state FIPS code.

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

Input Schema

Name	Required	Description
`ein`	No	Municipality EIN
`year`	No	Census year
`cbsa_code`	No	CBSA/metro area code
`state_fips`	No	State FIPS code

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?

With no annotations, the description carries the full burden of disclosing behavior, and it only reveals that this is a retrieval by one of several geographic identifiers. It says nothing about whether identifiers can be combined, what happens when none is supplied, permissions, or result shape, so an agent has little behavioral grounding.

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?

A single front-loaded sentence with no filler, and the lookup keys are stated immediately after the resource. It is efficient, though somewhat under-specified for a four-parameter tool rather than genuinely tight.

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

Completeness2/5

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

There is no output schema and no annotations, and the description does not clarify the semantics of combining four optional lookup keys or what an empty-key call does. For a tool whose only identifier logic is 'or', this leaves meaningful ambiguity unresolved.

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 the baseline is 3; each parameter is already documented. The description adds a useful hint that the three identifier parameters are alternatives ('or'), but it omits the year parameter entirely and gives no format details 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?

States a specific verb and resource ('Get economic and demographic data') and enumerates the three lookup keys, so an agent knows exactly what the tool returns. It does not explicitly differentiate itself from siblings like get_financials or get_scores_history, leaving the agent to infer the boundary.

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 only implied by the description; there is no statement of when to prefer this over get_municipality or get_financials, nor any prerequisites. The 'EIN, CBSA code, or state FIPS code' phrasing hints at alternative lookup paths but doesn't guide tool selection.

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

Deploy Server