Skip to main content
Glama

Stratalize Intelligence

Get Property Tax Benchmark

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, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds genuinely new information beyond that: the data source (Lincoln Institute of Land Policy) and the per-call cost ($0.02 USDC), which matters for invocation decisions. It does not state data vintage or whether values are precomputed or live, which keeps it below 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?

The content is front-loaded with the actual data delivered and lists the source and price at the end, which reads cleanly. The sentence 'Property tax is the largest controllable operating expense for most commercial properties' is motivational framing rather than operative instruction and does not fully pay for its space. Nothing is redundant, though.

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 small read-only benchmark tool with two parameters and no output schema, the description covers the substance an agent needs: the metrics returned, the segmentation dimensions, the data source, and the cost. The material gap is the response shape and time period, which must be inferred. That is a moderate rather than crippling omission given how simple the tool is.

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 50%: the state parameter is documented in-schema and the property_type parameter has an enum of commercial/residential/industrial/multifamily but no description. The phrase 'by state and property type' confirms that both act as segmentation filters, but it does not explain the consequence of omitting the optional property_type, nor the two-letter state format. That is baseline-level alignment at best.

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 description names a specific resource (property tax benchmarks) and enumerates the metrics returned: effective tax rates by state and property type, assessment ratios, and appeal success rates. That is far more than a restatement of the name. It does not, however, explicitly distinguish itself from the close sibling get_property_operating_benchmark, so an agent must infer the split between tax expense and broader operating expense.

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?

Usage is only implied, through the audience statement 'For property owners, asset managers, and acquisition teams' and the note that property tax is a large controllable operating expense. There is no explicit when-to-use, no when-not-to-use, and no named alternative such as the property operating benchmark. An agent gets a plausible context but must decide on its own whether to call this or a sibling.

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