Skip to main content
Glama

BRAINIAC Property Intelligence

Detect duplicate listings

property-intelligence_listing-duplicate-detect
Read-onlyIdempotent

Compare at least two supplied listings. The same address is a duplicate. The same price, currency, and bedroom count is only a possible match. Price $0.04 USDC. POST /api/v1/property-intelligence/listing-duplicate-detect. An unpaid call returns the x402 payment terms and does not run.

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": {
      "listings": "<listings>"
    },
    "name": "property-intelligence_listing-duplicate-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
listingsYeslistings, array. Required.

Output Schema

NameRequiredDescriptionDefault
pairsNopairs. Array.
statusNostatus. String.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
officialValuationNoofficialValuation. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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 open-world behavior, and the description adds information annotations cannot express: a $0.04 USDC cost, the x402 payment flow, and the critical fact that an unpaid call returns payment terms without executing. That last point materially changes how an agent must sequence calls.

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?

Five short sentences, front-loaded with the comparison action and its matching rules before the cost and payment caveats. Little is wasted; the POST endpoint path is marginal filler but not enough to hurt scannability.

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?

For a single-parameter tool with a full schema and an output schema, the description covers the input precondition, matching semantics, cost, and payment failure mode. The only unresolved gap is how more than two listings are compared — pairwise versus grouped — which an agent might want to know but can likely infer from the response.

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?

Schema coverage is 100%, so field-level documentation is already handled and the baseline is 3. The description goes beyond that by explaining how the fields are used in comparison logic — address determines a duplicate, while price, currency, and bedrooms only indicate a possible match — which the schema alone does not convey.

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 opens with a specific verb and resource ("Compare at least two supplied listings") and immediately defines the duplicate-detection rules for address matches and weaker price/currency/bedroom matches. That makes it clearly distinct from the extract, analyze, and normalize siblings without needing to name them.

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?

"Compare at least two supplied listings" gives an implied input precondition, but there is no explicit when-to-use guidance, no statement of when duplicate detection is inappropriate, and no routing to any alternative tool. Usage is inferable from the purpose rather than stated.

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