Skip to main content
Glama

Find land by owner name

find_land_by_owner
Read-onlyIdempotent

List the parcels a county records under an owner's name (owner, as on the tax bill, usually last name first), in one county (state and county), so the person can add theirs to Fabrica (Sepolia Testnet) with add_land (parcelNumber, state, county). Returns up to 10 parcels, each with its parcel number, recorded owner, address, acres, whether it is already on Fabrica and the fabrica.land link that adds it, and whether the owner has more. Reads county records only; nothing is created or changed. Meant for the person's own land. Needs the person to be signed in.

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": {
      "owner": "<owner>",
      "state": "<state>",
      "county": "<county>"
    },
    "name": "find_land_by_owner"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerYesThe owner's name as the county records it, usually last name first as on the tax bill (e.g. 'Smith John' or 'Smith Family Trust'). A person, a couple, a trust or a company.
stateYesTwo-letter state
countyYesCounty name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

The read-only and idempotent annotations already cover the safety profile, and 'Reads county records only; nothing is created or changed' largely restates them. What the description genuinely adds is the result cap of 10 parcels, the enumeration of returned fields, the 'has more' flag, and the sign-in requirement — useful but not deep behavioral disclosure.

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?

Purpose is front-loaded in the first clause, followed by short sentences for returns, side-effect profile, intent, and auth. The return-value enumeration is dense and partly redundant with the schema-provided params, but nothing is wasted enough to obscure the core instruction.

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?

With no output schema, the description compensates well by listing returned fields and the 10-parcel cap plus the 'has more' indicator, and it covers the auth prerequisite and the follow-up tool. Only minor gaps remain, such as what happens on ambiguous owner names or zero matches.

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% and each parameter already carries its own description, including the last-name-first convention for owner. The description reinforces the owner formatting and the single-county constraint but introduces no new syntax or edge-case meaning, 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?

States a specific verb and resource ('List the parcels a county records under an owner's name') plus the scoping constraints (one county, given state and county). It also names the downstream tool add_land with its arguments, so an agent can see exactly where this fits relative to siblings like search_land or find_us_parcel.

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?

Gives clear context: 'Meant for the person's own land,' requires the user to be signed in, and routes the result onward to add_land. It stops short of explicitly excluding alternatives such as search_land or find_us_parcel, so the when-not-to-use case is left implicit.

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.