Skip to main content
Glama

get_property_tax_benchmark

Read-only

Property tax benchmarks — effective tax rates by state and property type, assessment ratios, and appeal success rates. Source: Lincoln Institute of Land Policy. For property owners, asset managers, and acquisition teams. Property tax is the largest controllable operating expense for most commercial properties. $0.02 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter US state code
property_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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, so the description is free to add what they cannot: the data provenance (Lincoln Institute of Land Policy) and the per-call cost of $0.02 USDC. It still does not say what happens if a state has no data or how property_type omission is handled, keeping it short of a 5.

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?

Front-loaded with the metric list, then provenance, audience, and price – efficient ordering with no wasted sentences except the marketing-style claim that property tax is 'the largest controllable operating expense', which does little for tool selection.

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?

For a two-parameter read-only benchmark lookup with no output schema, the description covers what data comes back, its source, and its cost. The remaining gap is output shape and empty-result behavior, which is minor at this complexity.

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 50% – state is documented while property_type carries only an enum with no prose. The description recovers some meaning by stating results are broken out 'by state and property type', but it never clarifies that property_type is optional nor what aggregation applies when it is omitted.

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?

Names the specific resource and enumerates the returned metrics: effective tax rates by state and property type, assessment ratios, appeal success rates. That is far more concrete than a tautology, but it never distinguishes itself from the adjacent get_property_operating_benchmark sibling, which shares the real-estate domain.

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

Usage Guidelines3/5

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

The line 'For property owners, asset managers, and acquisition teams' implies the use case through audience targeting, and the expense framing hints at why to call it. There is no explicit when-to-use/when-not-to-use guidance and no pointer to an alternative tool for related metrics.

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