Skip to main content
Glama

BRAINIAC Property Intelligence

Property overview

property-intelligence_overview
Read-onlyIdempotent

Retrieve available planning and heritage information for a property using UPRN, coordinates, or postcode. Price $0.05 USDC. POST /api/v1/property-intelligence/overview. An unpaid call returns the x402 payment terms and does not run.

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": "property-intelligence_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
uprnNouprn, string. Optional.
latitudeNolatitude, number, from -90 to 90. Optional.
postcodeNopostcode, string. Optional.
longitudeNolongitude, number, from -180 to 180. Optional.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
overviewNooverview. Object.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds genuinely new behavioral context the annotations cannot convey: a $0.05 USDC price and the fact that an unpaid call returns x402 payment terms and does not execute. It stops short of describing what an empty/'no data available' response looks like.

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?

Four short sentences, front-loaded with the capability, then price, endpoint, and the unpaid-call caveat. Every sentence carries operational value with no filler.

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 an output schema present and annotations covering safety, the description supplies the missing pieces: identifier options and the payment/execution model. Minor gaps remain around multi-identifier precedence and what 'available' means when data is absent.

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 a 3 baseline applies, but the description adds meaning beyond the schema by presenting the identifiers as alternative lookup methods and implicitly signaling that an identifier is needed despite zero required parameters. It does not state precedence when multiple identifiers are supplied.

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 uses a specific verb ('Retrieve') and a concrete resource ('available planning and heritage information for a property'), plus the identifier inputs that drive it. It does not explicitly distinguish this broad overview from narrower siblings like planning-search or site-report, so it falls short of a 5.

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?

It tells the agent which identifiers can be used ('UPRN, coordinates, or postcode') and discloses the payment gate, but gives no when-to-use guidance relative to sibling tools such as details-normalize or due-diligence-report. Usage is implied rather than directed.

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