Skip to main content
Glama

get_property_assessment

Read-onlyIdempotent

Read county assessment records and their sources for a supported address or parcel ID. Keep missing facts unknown; commercial building area is not finished living area. Report comparisons as drafts with their evidence limits. They do not verify personal tax savings or authorize filing. For a property audit or a request to find tax-reduction routes, review opportunity_screen before concluding. A weak or held comparable-property analysis does not rule out independent relief, record corrections or billing research. Ask the next relevant unanswered targeted_questions item one at a time; use available_questions for relevant follow-ups. Accept none, not sure or skip, and do not repeat answered or skipped questions in this conversation unless the user changes the facts. After an answer, call recheck_property_opportunities for the same selected property and county with the accumulated explicit owner_answers and skipped_question_ids. Rechecks are stateless: resend still-applicable prior answers, preserve explicit false and empty arrays, and omit unknown or skipped fields instead of sending null or inventing a negative answer. Resend stable skipped_question_ids until the user supplies an answer or asks to revisit the question. Skips suppress prompts only and leave requirements unresolved. Do not transfer property-specific answers or skips to another property. When the user is done or skips the remaining questions, summarize supported research routes and missing evidence without treating unknowns as a denial. For a fact-only lookup, answer the requested fact and offer relevant screening without requiring an unrelated intake. Owner answers do not verify eligibility, savings, authority, payment or filing readiness.

Input Schema

NameRequiredDescriptionDefault
addressNoAlternative alias for property street address
county_keyNoOptional registered county key, such as hamilton. Searches only that county. A conflicting county prefix is rejected.
actual_sqftNoOptional owner-reported measured living area, in square feet
address_or_pidnYesFull street address or county parcel ID (e.g. '3731 Anderson Ave, Chattanooga, TN' or '157I L 001')
notice_appraised_valueNoOptional: New proposed appraised value from reassessment notice

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / actual_sqft / description
      Previous value: -"Optional: Actual measured living area in sq ft"New value: +"Optional owner-reported measured living area, in square feet"
    • changedInput schema / properties / county_key / description
      Previous value: -"Optional exact registered county adapter key, such as hamilton. Restricts lookup to that county and avoids unrelated county scans; conflicting explicit prefixes are rejected."New value: +"Optional registered county key, such as hamilton. Searches only that county. A conflicting county prefix is rejected."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the read-only annotations, it discloses important limits: missing facts stay unknown, commercial building area is not living area, comparisons are drafts with evidence limits, and the tool does not verify savings or authorize filing. It also explains that skips only suppress prompts and owner answers do not verify eligibility or filing readiness.

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

Conciseness2/5

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

The purpose is front-loaded, but the description is very long for a single read tool and mixes core behavior with detailed multi-turn workflow instructions. Several procedural points could be tightened or moved to agent-level guidance without losing essential tool-selection information.

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?

It covers the tool's domain, safety posture, and downstream workflow thoroughly despite having no output schema. However, it does not describe the return structure beyond 'records and their sources,' leaving some uncertainty about what a caller should expect back.

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 address, county_key, actual_sqft, address_or_pidn, and notice_appraised_value. The description adds some domain caveats relevant to square footage but does not provide parameter-specific syntax or selection guidance beyond the schema.

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?

The first sentence states a specific verb and resource: read county assessment records and their sources for an address or parcel ID. It also names related tools like opportunity_screen and recheck_property_opportunities, making the tool's role distinguishable from those siblings.

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

Usage Guidelines5/5

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

The description explicitly routes the agent: review opportunity_screen for tax-reduction routes, ask targeted_questions one at a time, call recheck_property_opportunities after answers, and handle fact-only lookups by answering and offering screening. It also states how to treat skipped questions and when to summarize rather than continue.

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.