Skip to main content
Glama

deal_scan

FREE. Postcode district (England & Wales): top 3 streets where recent Land Registry sales sit well below the district median for the same property type.

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": {
      "district": "<district>"
    },
    "name": "deal_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
districtYesPostcode district (outcode), e.g. M14, LS6, NG7

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose useful traits: cost (free), geographic scope (England & Wales), data provenance (Land Registry), comparison basis (district median, same property type), and a result cap (top 3). It omits how 'recent' is defined, behavior on thin-data districts, and whether an empty result is possible, which matters for a data tool with no annotation coverage.

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?

A single dense sentence with the most decision-relevant fact ('FREE') front-loaded, followed by scope and output. Nothing is redundant, though the parenthetical geography placement is slightly awkward.

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?

There is no output schema, so the description must convey return values; it conveys the count (top 3) and the entity (streets) but not the fields returned or how 'well below median' is scored or ranked. For a one-parameter tool this is adequate but leaves gaps an agent would want before presenting results.

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% and the parameter already documents the outcode format with examples, so the baseline is 3. The description adds a validity constraint beyond the schema: districts are limited to England & Wales, which tells the agent when a supplied outcode is out of scope.

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 names a concrete resource (postcode district streets with Land Registry sales below the district median) and a concrete output shape (top 3 streets), so an agent knows exactly what it retrieves. It doesn't explicitly contrast itself with the sibling deal_scan_full, though 'FREE' and 'top 3' imply a limited tier.

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?

Usage is only implied: 'FREE' and the capped 'top 3' hint that deal_scan_full exists for deeper results, but the description never says when to choose one over the other, nor any prerequisite such as needing a valid outcode. No exclusions or alternative routing are 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.