Skip to main content
Glama
Sign In
@munispot/mcp

@munispot/mcp

by chowdhury-raj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_scores_history

Retrieve a municipality’s MuniScore history across all available fiscal years using its EIN to review financial health trends over time.

Instructions

Get MuniScore history across all available fiscal years for a municipality.

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_scores_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
einYesEmployer Identification Number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose useful scope behavior: the result spans all available fiscal years, so an agent knows it is a historical series rather than a single-period lookup. It does not mention ordering, handling of missing years, permissions, or response format.

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?

It is a single front-loaded sentence with no wasted words. The scope ('across all available fiscal years') is stated efficiently.

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 simple one-parameter read tool this is adequate but not complete. Since there is no output schema, the description could say more about what the history records contain, such as scores per fiscal year and their ordering, but it does establish the key scope of 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?

The tool has one parameter and the schema description coverage is 100%, with the schema documenting the EIN field. The description adds no further meaning beyond identifying the municipality context, so baseline 3 is appropriate.

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 states a specific verb and resource: retrieving MuniScore history for a municipality across all fiscal years. It is clear what the tool does, though it does not explicitly differentiate itself from siblings such as get_financials or get_municipality.

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 'across all available fiscal years' — this tool is for historical trend retrieval rather than a current snapshot. However, it gives no explicit when-to-use guidance, no exclusions, and does not name alternatives like get_financials.

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