Skip to main content
Glama
Sign In
@munispot/mcp

@munispot/mcp

by chowdhury-raj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

compare_municipalities

Compare 2-10 U.S. municipalities side by side for a fiscal year to assess financial health, budget, debt, and key demographic indicators.

Instructions

Compare 2-10 municipalities side by side for a given fiscal year.

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": {
      "eins": "<eins>"
    },
    "name": "compare_municipalities"
  }
}

Input Schema

NameRequiredDescriptionDefault
einsYesArray of 2-10 EINs to compare
fiscal_yearNoFiscal year

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden, and it discloses almost nothing beyond what the schema already states. It is silent on what the comparison returns, how missing/unmatched EINs are handled, and what happens when the optional fiscal_year is omitted (current year? all years?). The '2-10' bound simply restates minItems/maxItems from the schema.

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 the verb first and zero filler; every clause (2-10 range, side-by-side, fiscal year) maps to a real constraint of the call.

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?

With no output schema and no annotations, the description is the only place to learn what a 'comparison' actually contains, and it never says which metrics or fields are compared or in what shape results come back. Adequate to trigger a call, insufficient to set expectations about the result.

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 schema already documents both parameters and the array bounds, making 3 the baseline. The description adds only the framing that the comparison is per fiscal year, with no detail on fiscal_year's default or accepted range.

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 (compare) and resource (municipalities) plus the cardinality bound and the fiscal-year scope, so an agent knows exactly what the tool produces. It does not explicitly differentiate itself from siblings like get_municipality or get_financials, though the name makes the comparison intent reasonably distinct.

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: 'side by side' suggests this is for multi-entity comparison rather than single-record lookup, which hints at when to prefer it over get_municipality. There is no explicit when-to-use, no exclusion of alternatives, and no statement about what to do if only one EIN is available.

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

Deploy Server

Other Tools