Skip to main content
Glama

lookup_property_tax

Read-onlyIdempotent

Look up retained county assessment observations for a supported address or parcel ID. Returns appraised/assessed amounts, separate classification and exemption observations, and explicitly labeled building area/year facts. Unsupported comparison models stay held. Conditional assessment comparisons do not establish personal savings, a verified market value, filing readiness or countywide certification.

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": {
      "address_or_pidn": "<address_or_pidn>"
    },
    "name": "lookup_property_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoAlternative alias for property street address
county_keyNoOptional exact registered county adapter key, such as hamilton. Restricts lookup to that county and avoids unrelated county scans; conflicting explicit prefixes are rejected.
actual_sqftNoOptional: Actual measured living area in sq ft (to detect assessor CAMA square footage measurement errors)
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 (if differing from current online county roll)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world behavior, so the safety profile is covered. The description adds value by enumerating the observation types returned and by explicitly disclaiming what the results do NOT establish (personal savings, verified market value, filing readiness, countywide certification), but the phrase 'Unsupported comparison models stay held' is opaque and the return/pagination behavior is undescribed.

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 opening sentence is well front-loaded and the return list is efficient. The final two sentences are dense disclaimer prose ('Conditional assessment comparisons do not establish...') whose wording is abstract and repeats the same non-guarantee idea twice, diluting rather than sharpening the definition.

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?

With a fully documented 5-parameter schema and no output schema, the description carries the burden of explaining returned observations, which it does reasonably well. It also sets expectations about what the results do not prove. Remaining gaps are guidance on when to prefer this lookup over the audit siblings and any note on supported county coverage.

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 coverage is 100%, so each parameter including county_key, actual_sqft and notice_appraised_value is already documented in the schema. The description adds only the notion of 'supported' addresses/parcels and 'explicitly labeled building area/year facts', which marginally frames actual_sqft but provides no syntax or format guidance beyond the schema. 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 first sentence names a specific verb and resource: 'Look up retained county assessment observations for a supported address or parcel ID.' It also enumerates what is returned (appraised/assessed amounts, classification and exemption observations, building area/year facts), which separates it from generic assessment tools. It does not, however, name or explicitly contrast with siblings such as get_property_assessment or audit_property_tax.

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

Usage Guidelines2/5

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

The description never states when to choose this tool over the many audit_* and get_property_* siblings. The only scoping hints are incidental ('a supported address or parcel ID', 'Unsupported comparison models stay held'), which describe limits rather than usage conditions or alternatives.

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.