Skip to main content
Glama

US Mortgage Calculator

Estimate property tax

calculate_property_tax
Read-onlyIdempotent

Annual and monthly property tax for a home, using a state's average effective rate. Also returns how that state ranks nationally and how its rate compares with the national average. For the mechanics behind the number — assessment basis, caps, exemptions, appeal deadlines — use get_state_mortgage_rules.

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": {
      "homePrice": "<homePrice>",
      "state": "<state>"
    },
    "name": "calculate_property_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesFull US state name, for example "Texas".
homePriceYesHome value in US dollars.

Output Schema

NameRequiredDescriptionDefault
stateYesState name.
caveatNoLimits of the estimate.
sourceNoWhere the rate comes from.
dataAsOfNoDate the underlying data refers to.
homePriceYesHome price used, in dollars.
disclaimerYesEstimate-only notice that should accompany any figure shown to a person.
annualPropertyTaxYesEstimated annual property tax, in dollars.
monthlyPropertyTaxYesEstimated monthly property tax, in dollars.
rankHighestToLowestNoRank of the state's rate, 1 being highest.
effectiveTaxRatePercentYesState average effective property tax rate, as a percentage.
nationalAverageRatePercentNoNational average rate, as a percentage.
comparedWithNationalAverageNoPlain-language comparison with the national average.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / homePrice / maximum
      Added value: +100000000
    • addedInput schema / properties / state / maxLength
      Added value: +64
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "description": "Annual and monthly property tax for a home price in one state.",
      +  "properties": {
      +    "annualPropertyTax": {
      +      "description": "Estimated annual property tax, in dollars.",
      +      "type": "number"
      +    },
      +    "caveat": {
      +      "description": "Limits of the estimate.",
      +      "type": "string"
      +    },
      +    "comparedWithNationalAverage": {
      +      "description": "Plain-language comparison with the national average.",
      +      "type": "string"
      +    },
      +    "dataAsOf": {
      +      "description": "Date the underlying data refers to.",
      +      "type": "string"
      +    },
      +    "disclaimer": {
      +      "description": "Estimate-only notice that should accompany any figure shown to a person.",
      +      "type": "string"
      +    },
      +    "effectiveTaxRatePercent": {
      +      "description": "State average effective property tax rate, as a percentage.",
      +      "type": "number"
      +    },
      +    "homePrice": {
      +      "description": "Home price used, in dollars.",
      +      "type": "number"
      +    },
      +    "monthlyPropertyTax": {
      +      "description": "Estimated monthly property tax, in dollars.",
      +      "type": "number"
      +    },
      +    "nationalAverageRatePercent": {
      +      "description": "National average rate, as a percentage.",
      +      "type": "number"
      +    },
      +    "rankHighestToLowest": {
      +      "description": "Rank of the state's rate, 1 being highest.",
      +      "type": "integer"
      +    },
      +    "source": {
      +      "description": "Where the rate comes from.",
      +      "type": "string"
      +    },
      +    "state": {
      +      "description": "State name.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "state",
      +    "homePrice",
      +    "effectiveTaxRatePercent",
      +    "annualPropertyTax",
      +    "monthlyPropertyTax",
      +    "disclaimer"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior, so the safety burden is covered. The description adds real value by disclosing that the result is based on a state's average effective rate (i.e., an approximation, not a parcel-specific bill) and by naming the returned comparisons.

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

Conciseness5/5

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

Three sentences, no filler, with the primary purpose front-loaded and the alternative tool routing placed last where it belongs. Every sentence carries distinct 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?

With an output schema present, the description need not detail return values, and it still summarizes the key outputs. The only minor gap is not stating that results are estimates of typical rates rather than a computed statutory bill, though 'average effective rate' gestures at this.

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%, with both state and homePrice documented in the schema, so the baseline is 3. The description adds only the framing that the rate is a state-level average effective rate, which slightly clarifies how state and homePrice combine but adds no format or validation detail 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?

States a specific verb and resource (annual and monthly property tax for a home) and enumerates the outputs, including state ranking and national-average comparison. This clearly separates it from sibling calculators like calculate_mortgage or estimate_closing_costs.

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?

Explicitly routes the agent to get_state_mortgage_rules for assessment basis, caps, exemptions, and appeal deadlines, which is a genuine exclusion clause. It does not discuss the other calculator siblings, but for a narrowly-scoped estimate tool the boundary that matters is the one it names.

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.

Resources