Skip to main content
Glama

Server Details

Maryland property-assessment fairness checks vs similar homes, with appeal windows and links.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over 74 days
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
ChatGPT
–
Claude
–

TDQS

A4.6/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so there is no possibility of confusing it with another tool. Its purpose—checking one Maryland property assessment for fairness—is clearly stated and self-contained.

Naming Consistency5/5

The single tool name check_assessment follows a clear verb_noun snake_case convention. With only one tool, there is no mixed or inconsistent naming pattern to penalize.

Tool Count4/5

The server appears intentionally narrow: one fairness-check operation for Maryland assessments. A single tool is slightly thin by general MCP standards, but it is well matched to this specific purpose rather than being trivial or arbitrary.

Completeness5/5

The tool covers the full described workflow: address/account matching, multiple-match and unit handling, parcel and uniformity data, verdict branches, appeal windows, roll freshness, and explicit error cases. No obvious lifecycle or operational gap is apparent for a read-only fairness snapshot.

Available Tools

1 tool
check_assessmentCheck fairness of a Maryland property assessmentA
Read-onlyIdempotent
Inspect

Fairness check for one Maryland property assessment against genuinely similar homes (same triennial reassessment group, similar size, lot and age, same zip), from a copy of the state's own assessment roll (SDAT) refreshed monthly. Input is a Maryland street address with its zip, its Maryland city or county, or MD, or an SDAT account id (acct); the city, county, state and zip can be written in the address itself (1 STATE CIR, ANNAPOLIS, MD 21401), a city or county narrows the match to that place the way a zip does, and MD alone matches the street across the whole state. A single match returns the parcel record, a uniformity object, a plain-language verdict, Maryland's appeal windows with official filing links, and honesty notes. In the parcel record, market_value is the full value an appeal argues about; taxable_now is the phased-in assessment for the Maryland tax year holding today (tax years run July 1 to June 30; taxable_now_tax_year gives its from and to dates, YYYY-MM-DD), and taxable_next with taxable_next_tax_year is the one for the tax year after; either pair is left out when the roll does not hold that year. The uniformity object gives BandSize (how many similar homes), where the assessment sits among them as percentiles (PctFMV for market value, PctImprPSF for improvement value per square foot, PctLand for land value), their medians (MedianFMV, MedianImprPSF, MedianLand), the median sales ratio of assessment to sale price (MedianSalesRatio) and its coefficient of dispersion (COD) over RatioSales sales dated RatioFromYear through RatioToYear (three calendar years ending with the year of the roll's newest sale dated on or before today), and Branch. RatioSales counts sales of $100,000 or more that the roll codes as arm's-length sales of one improved parcel; foreclosures, gifts, auctions, sales of several parcels for one price and sales of a vacant lot are left out. When the roll records no lot size or no year built for the home, the band skips that test: NotCompared names it (lot size or year built; both as lot size, year built) and the plain verdict's not_compared field says so in words. NotCompared is absent when every test ran. When the assessment sits high (PctFMV 75 or more) or low (below 25) and the home's rank on total value per square foot sits 3 or more in 10 from its rank on total value, the plain verdict's size field says so: total value is the rate per square foot times living area, so the difference comes from the home's size. Verdict branches: fair means the assessment is below the 75th percentile of similar homes (the plain headline calls it on the low side below the 25th and lower than almost all of them below the 10th, and the normal range otherwise); review means it is on the high side; elevated means it is higher than almost all of them; insufficient means fewer than 25 similar homes exist for a fair comparison, which is no finding either way. On the insufficient branch the percentile and median fields are 0, meaning not computed. A single-match or multiple_matches result also carries a roll object: as_of is the date the state last updated the roll and pulled is the date this copy was taken (both YYYY-MM-DD), overdue is true when this copy is more than 35 days old, and a field the server does not know is left out. MedianSalesRatio and COD are 0 when RatioSales is below 10, meaning no ratio is published. When several parcels share the address, the result is multiple_matches, listing parcels with their account ids; passing one of those ids as acct selects that parcel. The list is in unit order, each option carries unit (the unit as the roll writes it, such as UNIT 204) when the roll records one, and total gives how many parcels share the address; when more than 10 do (a condominium building, for instance), the list holds the first 10. A unit written after the street (100 HARBORVIEW DR UNIT 204, 100 HARBORVIEW DR #204, or as its own comma-separated part) narrows the match to that unit when the roll records units at the address, and a single match then carries parcel.unit; when the roll records units there and none is the unit written, the result is an error naming that unit, with no match list; a unit at an address where the roll records none is not applied. Every refusal and every miss below is a tool error: isError is true and the text content is the error message, with no verdict and no match list. When nothing matches, the result is an error; the roll writes addresses in its own form (e.g. 1 STATE CIR), so a miss can mean a different spelling, a town other than the one the roll records, or a zip other than the one the roll records, rather than a missing parcel. A zip is 5 digits; a ZIP+4 (21202-1234) is read as its first five digits, and a zip in the zip input takes precedence over one written in the address. A malformed zip or acct returns an error naming the expected form, a zip outside Maryland returns an error stating that only Maryland is covered, an address naming another state or territory returns an error stating that only Maryland is covered and naming that state as not covered yet, an address with no Maryland zip, city, county or state returns an error stating that only Maryland is covered and that a zip, city or county is needed, and an acct the roll does not hold returns an error stating that no parcel has that account id; none of these carries a verdict or a match list. Without a Maryland zip or MD, an address also gets the error asking for a zip, city or county when a comma-separated part after the street is not read as a Maryland place, a state, a zip, a unit or the US, such as a town Maryland lacks, another country or a state written as Miss. (100 MAIN ST, DOVER, KENT or 100 MAIN ST, LAUREL, MISS.), or when its county is written only as Co with no other Maryland place (1 MAIN ST, HOWARD CO). The check is a fairness snapshot of the public record, not an appraisal, and not legal advice; the official SDAT record is authoritative.

NameRequiredDescriptionDefault
zipNo5-digit zip; a ZIP+4 is read as its first five digits, and a whole JSON number up to 99999 is read as a zip with its leading zeros restored (1234 is 01234). Optional when the address carries a Maryland zip, city, county or state; a zip here takes precedence over one in the address. The same street address occurs in several Maryland towns, and a zip narrows the match
acctNoSDAT account id as returned in parcel.account_id or in a multiple_matches result: letters and digits (e.g. 020600002182004), with one space before the lot in Baltimore City (e.g. 0304121302 001); spaces in it are ignored, so 0304121302001 reads the same; when present it takes precedence over address. A JSON number is read as its digits, or with the leading zero a number cannot hold when that is the id on the roll; a number that names no single parcel is an error asking for the id as a string
addressNoMaryland street address in the form the roll uses (e.g. 1 STATE CIR), with any unit after the street (100 HARBORVIEW DR UNIT 204), followed by its Maryland city or county, the state, or the zip (e.g. 1 STATE CIR, ANNAPOLIS, MD 21401); an address with no Maryland zip, city, county or state, here or in the zip input, is not matched. An SDAT account id sent here alone (0304121302 001, 160500305131) is read as acct

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description adds substantial context: monthly roll refresh, as_of/pulled/overdue staleness, branch meanings, ratio methodology, unit handling, and error behavior. It does not contradict the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and most detail is relevant because no output schema exists, but the description is a dense single block that repeats some schema text and is longer than necessary. It is adequately organized but not concise.

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

Completeness5/5

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

With no output schema, the description fully explains parcel fields, uniformity fields, verdict branches, roll metadata, multiple_matches behavior, and error cases, including conventions such as zero meaning not computed. It leaves little ambiguity about how to invoke or interpret the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: unit narrowing, zip precedence, acct-as-address fallback, and malformed-input error forms. Some of this duplicates the schema, keeping it from a 5.

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 verb and resource: a fairness check of one Maryland property assessment against genuinely similar homes from the SDAT roll. The comparison basis and Maryland scope make the tool's purpose unmistakable, and there are no siblings to confuse it with.

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?

Explains supported input forms, Maryland-only coverage, and clarifies that this is a fairness snapshot rather than an appraisal or legal advice. It does not provide an explicit 'use this when' instruction or name alternatives, though none exist in the sibling list.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedcheck_assessment2 fields changed
      • changedInput schema / properties / acct / description
        Previous value: -"SDAT account id as returned in parcel.account_id or in a multiple_matches result: letters and digits (e.g. 020600002182004), with one space before the lot in Baltimore City (e.g. 0304121302 001); spaces in it are ignored, so 0304121302001 reads the same; when present it takes precedence over address"New value: +"SDAT account id as returned in parcel.account_id or in a multiple_matches result: letters and digits (e.g. 020600002182004), with one space before the lot in Baltimore City (e.g. 0304121302 001); spaces in it are ignored, so 0304121302001 reads the same; when present it takes precedence over address. A JSON number is read as its digits, or with the leading zero a number cannot hold when that is the id on the roll; a number that names no single parcel is an error asking for the id as a string"
      • changedInput schema / properties / address / description
        Previous value: -"Maryland street address in the form the roll uses (e.g. 1 STATE CIR), with any unit after the street (100 HARBORVIEW DR UNIT 204), followed by its Maryland city or county, the state, or the zip (e.g. 1 STATE CIR, ANNAPOLIS, MD 21401); an address with no Maryland zip, city, county or state, here or in the zip input, is not matched"New value: +"Maryland street address in the form the roll uses (e.g. 1 STATE CIR), with any unit after the street (100 HARBORVIEW DR UNIT 204), followed by its Maryland city or county, the state, or the zip (e.g. 1 STATE CIR, ANNAPOLIS, MD 21401); an address with no Maryland zip, city, county or state, here or in the zip input, is not matched. An SDAT account id sent here alone (0304121302 001, 160500305131) is read as acct"
  2. 1 tool update
    • Changedcheck_assessment3 fields changed
      • changedInput schema / properties / acct / description
        Previous value: -"SDAT account id, letters and digits with no dashes or spaces (e.g. 04121302001), as returned in parcel.account_id or in a multiple_matches result; when present it takes precedence over address"New value: +"SDAT account id as returned in parcel.account_id or in a multiple_matches result: letters and digits (e.g. 020600002182004), with one space before the lot in Baltimore City (e.g. 0304121302 001); spaces in it are ignored, so 0304121302001 reads the same; when present it takes precedence over address"
      • changedInput schema / properties / address / description
        Previous value: -"Street address in the form the roll uses, e.g. 1 STATE CIR, without unit number or city"New value: +"Maryland street address in the form the roll uses (e.g. 1 STATE CIR), with any unit after the street (100 HARBORVIEW DR UNIT 204), followed by its Maryland city or county, the state, or the zip (e.g. 1 STATE CIR, ANNAPOLIS, MD 21401); an address with no Maryland zip, city, county or state, here or in the zip input, is not matched"
      • changedInput schema / properties / zip / description
        Previous value: -"5-digit zip; a ZIP+4 is read as its first five digits. Optional, but the same street address occurs in several Maryland towns, and a zip narrows the match"New value: +"5-digit zip; a ZIP+4 is read as its first five digits, and a whole JSON number up to 99999 is read as a zip with its leading zeros restored (1234 is 01234). Optional when the address carries a Maryland zip, city, county or state; a zip here takes precedence over one in the address. The same street address occurs in several Maryland towns, and a zip narrows the match"
  3. 1 tool update
    • Changedcheck_assessment2 fields changed
      • changedInput schema / properties / acct / description
        Previous value: -"SDAT account id, as returned in parcel.account_id or in a multiple_matches result; when present it takes precedence over address"New value: +"SDAT account id, letters and digits with no dashes or spaces (e.g. 04121302001), as returned in parcel.account_id or in a multiple_matches result; when present it takes precedence over address"
      • changedInput schema / properties / zip / description
        Previous value: -"5-digit zip; optional, but the same street address occurs in several Maryland towns, and a zip narrows the match"New value: +"5-digit zip; a ZIP+4 is read as its first five digits. Optional, but the same street address occurs in several Maryland towns, and a zip narrows the match"
  4. 1 tool update
    • Changedcheck_assessment3 fields changed
      • changedInput schema / properties / acct / description
        Previous value: -"SDAT account id from a prior multiple_matches result (wins over address)"New value: +"SDAT account id, as returned in parcel.account_id or in a multiple_matches result; when present it takes precedence over address"
      • changedInput schema / properties / address / description
        Previous value: -"Street address as the roll writes it, e.g. 1 STATE CIR (no unit numbers, no city)"New value: +"Street address in the form the roll uses, e.g. 1 STATE CIR, without unit number or city"
      • changedInput schema / properties / zip / description
        Previous value: -"5-digit zip (recommended; addresses repeat across Maryland)"New value: +"5-digit zip; optional, but the same street address occurs in several Maryland towns, and a zip narrows the match"
  5. 1 tool update
    • First observedcheck_assessment

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to look up county assessor public records for properties, check MLS discrepancies against public data, and discover new county assessor sources, all via a local MCP server for real-estate appraisal workflows.
    6
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables source-backed property assessment research and draft assessment comparisons for supported pilot jurisdictions, including free private veteran review PDFs from explicitly selected saved reviews with unanswered questions shown, while keeping retained county facts, owner reports, and optional permitted VA observations distinct.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Provides access to comprehensive US property data, including automated valuations, tax history, comparable sales, and ownership details, enabling real estate analysis and market insights.
    418 npm
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    Provides free property and parcel intelligence using official US government data APIs, county assessor records, and live listings, with tools for hazard risk checks, affordability calculations, and parcel ranking.
    -
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources