Skip to main content
Glama

Appeal Draft – Twin Cities property tax appeal

Minnesota property tax appeal dates and steps (2027 valuation notices, open book, local and county boards, Tax Court)

property_tax_appeal_dates
Read-onlyIdempotent

When Minnesota valuation notices mail, when open book and Local Board of Appeal and Equalization meetings run, when the County Board meets and when the Tax Court deadline falls, each with its official source, plus the county's own steps and assessor phone for Hennepin (Minneapolis), Ramsey, Anoka, Dakota, Scott and Washington. Use for 'when can I appeal my property taxes', 'what is the deadline to appeal my assessment in Minnesota', 'when do 2027 valuation notices come out'. Minnesota only.

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

Input Schema

NameRequiredDescriptionDefault
countyNoOptional: a Minnesota county, e.g. 'Ramsey' or 'Hennepin'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish this is a safe, idempotent, read-only lookup, so the description's job is to add operational context, which it does: every date carries an official source, county output adds procedural steps and an assessor phone number, and county-level detail is explicitly limited to Hennepin, Ramsey, Anoka, Dakota, Scott and Washington. It does not say what happens for an unlisted county or how the year scope is determined, which keeps it from a 5.

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 returned milestones are front-loaded in the first clause and the scope restriction is placed last, which is the right ordering. The list of counties and the three example queries are long but each earns its place by pinning down coverage and intent; the wording is dense rather than padded.

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

Completeness4/5

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

For a single-optional-parameter, read-only lookup with no output schema, the definition covers what is returned, sourcing, county-specific extras and geographic limits, which is enough for an agent to call it correctly. The only residual gap is what the tool does when given a county outside the six listed.

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?

There is only one optional parameter and the schema already documents it at 100% coverage, giving a baseline of 3. The description adds modest value by enumerating the six counties for which county-specific steps and phone numbers exist, effectively signaling which values produce richer output, but it does not explain behavior for other counties.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource (Minnesota property tax appeal dates and procedural steps) and enumerates exactly which milestones are returned: valuation-notice mailings, open book, Local Board, County Board, and Tax Court deadline. This clearly separates it from the sibling tools, which deal with assessment values and area ratios rather than calendars.

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

Usage Guidelines4/5

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

Supplies three concrete trigger phrases ('when can I appeal my property taxes', 'what is the deadline to appeal my assessment in Minnesota', 'when do 2027 valuation notices come out') that tell the agent when to reach for it. It also bounds applicability with 'Minnesota only', but never names the sibling tools or says when to prefer them instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.