Skip to main content
Glama

BRAINIAC Property Intelligence

Generate site report

property-intelligence_site-report
Read-onlyIdempotent

Generate a comprehensive site report combining constraints, brownfield land, and planning applications. Price $0.10 USDC. POST /api/v1/property-intelligence/site/report. 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_site-report"
  }
}

Input Schema

NameRequiredDescriptionDefault
uprnNouprn, string. Optional.
latitudeNolatitude, number, from -90 to 90. Optional.
postcodeNopostcode, string. Optional.
longitudeNolongitude, number, from -180 to 180. Optional.
includeBrownfieldNoincludeBrownfield, boolean. Required.
includePlanningApplicationsNoincludePlanningApplications, boolean. Required.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds valuable context beyond annotations: the $0.10 USDC price, the POST endpoint, and the fact that an unpaid call returns x402 payment terms and does not run. This meaningfully informs the agent about cost and failure behavior.

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?

The description is four compact sentences with the core purpose front-loaded, followed by cost, endpoint, and payment-gate behavior. Every sentence earns its place and there is no unnecessary wording.

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 a full input schema, an output schema, and rich annotations, the description covers the key purpose, cost, and payment gating. It is complete enough for correct invocation, though it could better distinguish this report from sibling report tools.

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

Parameters3/5

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

Schema description coverage is 100%, so all six parameters are already documented in the schema. The description mentions brownfield and planning applications, which map to existing parameters, but it adds no syntax, format, or selection guidance beyond the schema.

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: 'Generate a comprehensive site report combining constraints, brownfield land, and planning applications.' It clearly conveys the report's scope. However, it does not explicitly differentiate this report from the sibling due-diligence-report or constraints-check beyond listing included sections.

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?

The description gives no explicit guidance on when to use this tool versus alternatives, nor does it name any sibling tool or exclusion condition. Payment information is provided, but usage selection guidance is absent.

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