Skip to main content
Glama

Get property tax status

get_land_tax_status
Read-onlyIdempotent

Get whether a property's taxes are current, past due or unknown, according to Fabrica's Property checks: the status, which signal it comes from (the Property Taxes Current check, the DeFi lending pool's block reason, both, or a note that they disagree), when it was checked and when the checks expire, and whether it limits borrowing. It is a data lookup, not the county's own statement; the amount due and the due date are not available.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_land_tax_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoProperty slug from the URL
tokenIdNoThe token ID of the property

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, yet the description adds substantial value beyond them: it discloses that results are derived from Fabrica's checks rather than county records, that signals can conflict or disagree, that checks have an expiration, and that the output flags whether borrowing is limited. Negative scope (no amount due, no due date) prevents an agent from expecting data that isn't there.

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?

Effectively two sentences, with the outcome vocabulary (current, past due, unknown) front-loaded before the provenance details. The first sentence is long and comma-heavy, cataloguing four separate signal cases in one breath, but every clause carries information an agent would otherwise have to guess.

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?

There is no output schema, so the description carries the return-value burden and does it well by naming status, source, check timestamps, expiry and borrowing impact. The remaining gap is minimal but real: with zero required parameters, it never states that at least one of slug or tokenId must be supplied to identify the property.

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 both slug and tokenId are already documented in the schema and the description correctly does not repeat them. Baseline 3 applies; the description adds no format or precedence guidance for choosing between the two identifiers, which is a real gap given that neither is marked required.

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?

States a specific verb and resource (get a property's tax status) and enumerates the possible values (current, past due, unknown) plus the provenance of each signal. It also draws a clear boundary against the county's own record, which implicitly separates it from document/valuation siblings. It does not name a sibling tool by name, so differentiation is achieved by description rather than explicit routing.

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 description implies when the tool is appropriate by framing it as a borrowing-relevant data lookup and by stating what is NOT available (amount due, due date). However, it never says when to use this versus explain_property_checks or get_land_property, and gives no prerequisites about needing a slug or tokenId.

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.