Skip to main content
Glama

Appeal Draft – Twin Cities property tax appeal

Does the county over-assess homes here? Assessment ratio by ZIP, city or county (Twin Cities)

assessment_ratio_by_area
Read-onlyIdempotent

The assessment ratio (county value / sale price) for recorded home sales in a Twin Cities ZIP, city or county: the share of sold homes the county valued above their sale price, the median ratio, and how it ranks against the rest of the metro, plus the IAAO uniformity measures by county and the gap between cheaper and dearer homes. Use for 'does Ramsey County over-assess homes', 'are assessments too high in 55104', 'how accurate are property assessments in Roseville'. Covers houses and townhouses in Ramsey, Anoka, Dakota, Scott and Washington counties and the City of Minneapolis.

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": {
      "area": "<area>"
    },
    "name": "assessment_ratio_by_area"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaYesA ZIP (55104), a city (Roseville, Saint Paul) or a county (Ramsey)

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 declare readOnlyHint=true and destructiveHint=false, and the description adds genuinely useful scope context: only recorded home sales, only houses and townhouses, and a fixed five-county plus Minneapolis footprint. It does not state the lookback window for sales or minimum sample-size behavior, which would matter for interpreting a ratio or rank.

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 output content is front-loaded in the opening clause before the example queries, and every sentence contributes either output definition or scope. The first sentence is dense with stacked clauses, slightly taxing to parse, but there is no filler or repetition.

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?

Because there is no output schema, the description must carry return-value meaning and it does: the four analytic components plus county-level uniformity measures are all named. Coverage boundaries are stated too. The notable omission is the time period of the sales underlying the ratio and rank, which an agent would need to frame results accurately.

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% and the single 'area' parameter documents its accepted formats (ZIP, city, county) with examples. The description repeats the same three formats without adding parsing rules, ambiguity handling, or fallback behavior, so it does not exceed the schema-driven baseline.

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?

States a specific metric with its formula (county value / sale price) and enumerates exactly what the response contains: share of homes assessed above sale price, median ratio, metro rank, IAAO uniformity measures, and the cheap-vs-expensive gap. It also names the geographic resolution (ZIP, city, county) which distinguishes it cleanly from per-property siblings like check_property_assessment.

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?

Three concrete example phrasings ('does Ramsey County over-assess homes', 'are assessments too high in 55104', 'how accurate are property assessments in Roseville') make the intended question type unambiguous, and the coverage sentence scopes the five counties plus Minneapolis. There is no explicit when-not-to-use note or named alternative for single-address lookups, so it stops short of a 5.

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.