Skip to main content
Glama
Sign In

Fabrica (Sepolia testnet)

by land.fabrica
OverviewDiscussionsAdmin

Check county coverage

check_county_coverage
Read-onlyIdempotent

Whether a US county (or a whole state) can be added to Fabrica online: supported, notConfigured or unsupported, and for a supported county the deed and forms the owner signs (and which are notarized), witness requirements, the questions the owner is asked, and the steps to add a property. Answers from a table of Fabrica's rules for adding property as of 2026-10-16, refreshed by hand, so each answer carries that date; the add-property page on fabrica.land is the live answer. Give a 5-digit county FIPS, or a two-letter state with or without a county. No fee amounts (ask_fabrica has them) and no owner data.

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": "check_county_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
fipsNo5-digit county FIPS code, e.g. '06065'
stateNoTwo-letter US state code, e.g. 'CA'
countyNoCounty name, e.g. 'Riverside' (with state)
ownerTypeNoWho holds title today: individual (default), entity or concurrent (co-owners)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it discloses the data provenance (a hand-refreshed table of Fabrica's rules as of 2026-10-16), that every answer carries that date, and that the add-property page on fabrica.land is the live authoritative answer. That staleness caveat is exactly the behavioral context an agent needs before trusting results.

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 answer categories and input forms are front-loaded in the first two sentences, and the exclusions close it out. It is dense and somewhat run-on, but nearly 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.

Completeness5/5

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

With no output schema, the description carries the return-value burden and does so: it names the three status values and lists the payload components for a supported county, plus the date stamp on every answer. Nothing essential for correct invocation or interpretation appears missing.

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 patterns, examples and an enum for ownerType already documented. The description restates the FIPS/state shapes and implies ownerType matters ('the deed and forms the owner signs', questions asked of the owner) but never explains how individual/entity/concurrent changes the result, so it adds little 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?

The description names a specific verb and resource (checking whether a US county or state can be added to Fabrica online) and enumerates the exact return categories: supported, notConfigured, unsupported. It also tells the agent what the answer contains for a supported county—deed, forms, notarization, witness requirements, owner questions, add steps—which distinguishes it cleanly from siblings like ask_fabrica.

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?

It gives concrete input guidance ('Give a 5-digit county FIPS, or a two-letter state with or without a county') and explicitly redirects fee questions to ask_fabrica and excludes owner data. What it lacks is an explicit statement of when NOT to call it for other adjacent questions (e.g., parcel lookup, valuation), so it is clear context without full exclusions.

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

All Fabrica (Sepolia testnet) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources