Skip to main content
Glama

BRAINIAC Property Intelligence

Check planning constraints

property-intelligence_constraints-check
Read-onlyIdempotent

Check specific planning constraints (conservation areas, listed buildings, flood risk, etc.) for a location. Price $0.05 USDC. POST /api/v1/property-intelligence/constraints/check. 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_constraints-check"
  }
}

Input Schema

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

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the price, the POST endpoint, and importantly that an unpaid call returns x402 payment terms and does not execute. This is valuable behavioral context not available from the structured fields, though it does not cover rate limits or result shape.

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?

The description is short and front-loads the purpose, followed by price and endpoint details. Every sentence carries useful information, though the endpoint string is somewhat operational rather than agent-facing.

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 annotations, a complete input schema, and an output schema present, the description supplies the extra operational facts an agent needs, especially the payment behavior. It is largely complete, though location-input expectations such as using UPRN versus coordinates are left to the schema.

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 the four parameters are already documented in the schema. The description lists example constraint categories but does not add syntax, format, or selection guidance beyond what the schema provides, so baseline 3 is appropriate.

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 gives a specific verb and resource: checking named planning constraints such as conservation areas, listed buildings, and flood risk for a location. It is clear what the tool does, though it does not explicitly distinguish itself from the many sibling property-intelligence tools.

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?

It implies the tool is used for location-based planning-constraint checks but gives no explicit when-to-use or when-not-to-use guidance. No sibling alternative is named, so an agent must infer routing from the tool name alone.

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