Skip to main content
Glama

BRAINIAC Property Intelligence

Search planning applications

property-intelligence_planning-search
Read-onlyIdempotent

Search planning applications by local planning authority, date range, or other filters. Price $0.05 USDC. POST /api/v1/property-intelligence/planning/search. 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_planning-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNolimit, integer, from 1 to 100. Required.
offsetNooffset, integer, from 0 to 9007199254740991. Required.
startDateDayNostartDateDay, integer, from 1 to 31. Optional.
startDateYearNostartDateYear, integer, from 2000 to 2100. Optional.
startDateMatchNostartDateMatch, string, one of since, on, before. Optional.
startDateMonthNostartDateMonth, integer, from 1 to 12. Optional.
localPlanningAuthorityNolocalPlanningAuthority, string. Optional.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive, open-world operation, and the description is consistent with that. It adds behavior the annotations do not carry: the $0.05 USDC price, the concrete POST endpoint, and the crucial fact that an unpaid call returns x402 payment terms without executing — exactly the kind of operational detail an agent needs before calling.

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?

Three short sentences, front-loaded with purpose and followed by the two operational facts that matter (price and payment-failure behavior). No filler, though the endpoint path is somewhat redundant for an agent that only invokes the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and the annotations cover the safety profile. Combined with the disclosed price and unpaid-call semantics, an agent has everything needed to decide to call and to interpret a payment-required response.

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 coverage is 100%, so every parameter is already documented, and the description only restates the filter themes (authority, date range, other filters) without adding format or interaction detail, such as how startDateMatch combines with the day/month/year fields. Baseline 3 is appropriate given the schema does the heavy lifting.

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?

States a specific verb and resource ('Search planning applications') and names the primary filter axes (local planning authority, date range, other filters). It is clearly distinguishable from siblings like constraints-check or listing-extract, though it does not explicitly contrast itself with any named alternative.

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 implied by the domain wording — an agent can infer this is the tool for querying planning-application records — but there is no explicit when-to-use versus when-not-to-use guidance, and no prerequisites or exclusions are stated beyond the payment note.

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