Skip to main content
Glama

Black Label Real Estate Website MCP

estate_stats

Read-onlyIdempotent

Corpus totals for the public-records API (total_records, live_properties, archived_properties, states, counties, freshness).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds the return field set, which matters because there is no output schema, but says nothing about authentication, rate limits, or whether the counts are cached/point-in-time.

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?

One sentence, front-loaded with the scope and followed by a compact parenthetical field list. Every element carries information the agent needs given the absence of an output schema; the parenthetical is dense but justified.

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

Completeness3/5

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

For a zero-parameter, annotation-covered read tool, the definition is nearly sufficient, and listing the returned metrics compensates for the missing output schema. The remaining gap is selection guidance versus estate_coverage, which an agent comparing siblings would need.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the empty schema with additionalProperties=false is self-explanatory. No credit or penalty applies beyond the baseline.

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 resource — corpus-level totals for the public-records API — and enumerates the exact metrics returned (total_records, live_properties, archived_properties, states, counties, freshness). This distinguishes it from the per-entity siblings like estate_owner and estate_parcel, though it does not address how it relates to the similarly named estate_coverage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no exclusions, and no mention of alternatives. The closest potential overlap, estate_coverage, is not referenced at all, leaving the agent to infer which of the two supplies corpus-level counts.

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