Skip to main content
Glama
Fabrica MCP Server

Fabrica MCP Server

Official
by fabrica-land

Get property tax status

get_tax_status
Read-onlyIdempotent

Check a tokenized property's tax status on Fabrica: current, past due, or unknown, with source, expiry times, and whether it limits borrowing.

Instructions

Get whether a tokenized 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_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. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds real value beyond that: the check's provenance ('Property Taxes Current check, the DeFi lending pool's block reason, both, or a note that they disagree'), expiry semantics, and the borrowing-limit implication.

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-loads the core answer (current/past due/unknown) before the supporting detail, and every clause carries information about returned signals or scope limits. It is a long single sentence, but trimming it would remove genuinely useful distinctions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description effectively enumerates the return payload: status, signal source, check timestamp, expiry, and borrow impact. Combined with the explicit limitation about county amounts, an agent has everything needed to call and interpret this tool.

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% with only two parameters (slug, tokenId), both already documented in the schema. The description adds no parameter-level syntax or format detail, so the baseline 3 applies.

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?

Names a specific verb (get) and resource (tax status) and enumerates the exact domain values returned: current, past due, or unknown. It is clearly distinguishable from siblings like get_property or get_valuation because it scopes to tax standing on a tokenized property.

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 frames the tool as 'a data lookup, not the county's own statement,' and states what is not available (amount due, due date), which sets expectations about when to rely on it. It does not, however, name an alternative sibling or state a when-not-to-use condition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.