Skip to main content
Glama

Black Label Real Estate Website MCP

estate_parcel

Read-onlyIdempotent

Exact parcel lookup by state and parcel_id.

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>",
      "parcel_id": "<parcel_id>"
    },
    "name": "estate_parcel"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYes
parcel_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and idempotency profile is fully covered by structured data. The description adds essentially nothing behavioral beyond implying no fuzzy matching — it does not say what happens when the parcel does not exist, whether state codes are normalized, or where the data comes from despite openWorldHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with the keying constraint front-loaded and no filler. Nothing is wasted.

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?

Placeholder.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so both required parameters carry no documentation in the schema and the description must compensate. It only restates the parameter names as lookup keys, giving no format guidance for state (abbreviation vs full name, case sensitivity) or parcel_id (APN format, separators, leading zeros) — both of which are common sources of failed lookups.

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 states a specific verb and resource ('Exact parcel lookup') and names the two keying inputs, which distinguishes it from the fuzzy sibling estate_search. It stops short of naming that sibling explicitly, but an agent can still tell this is a precise single-record fetch rather than a search.

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 word 'Exact' implies this tool should be used only when the caller already knows a state + parcel_id, whereas partial or descriptive queries belong in estate_search, but that alternative is never stated. Usage is inferable rather than explicit, and no prerequisites or failure conditions are given.

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