Skip to main content
Glama

BRAINIAC Property Intelligence

Read area context

property-intelligence_area-context
Read-onlyIdempotent

Look up the OpenStreetMap place for a supplied address or coordinates. Planning, crime, ownership, and valuation stay unavailable. Price $0.04 USDC. POST /api/v1/property-intelligence/area-context. 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_area-context"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoaddress, string, length 1 to 300. Optional.
latitudeNolatitude, number, from -90 to 90. Optional.
longitudeNolongitude, number, from -180 to 180. Optional.

Output Schema

NameRequiredDescriptionDefault
cityNocity. String.
crimeNocrime. String.
statusNostatus. String.
countryNocountry. String.
findingsNofindings. Array.
latitudeNolatitude. Number.
localityNolocality. String.
planningNoplanning. String.
postcodeNopostcode. String.
checkedAtNocheckedAt. String.
longitudeNolongitude. Number.
ownershipNoownership. String.
valuationNovaluation. String.
displayNameNodisplayName. String.
limitationsNolimitations. Array.
officialValuationNoofficialValuation. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly/idempotent/openWorld) by disclosing the monetization model: $0.04 USDC per call, a POST endpoint, and the concrete failure mode that an unpaid call returns x402 payment terms and does not execute. Cost and payment-gating behavior are exactly the kind of operational context annotations cannot carry.

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?

Four short sentences, purpose front-loaded, followed by scope, price, endpoint, and payment behavior. The raw endpoint path ('POST /api/v1/property-intelligence/area-context') largely duplicates information already implied by the tool name and slightly dilutes the opening.

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?

A read-only lookup with a full output schema and rich annotations, plus cost and payment-failure disclosure, so an agent has nearly everything needed. The remaining gap is the ambiguity of zero required parameters: the description never states that one of address or coordinates must be provided.

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% and each of the three parameters has bounds documented, so the schema does the heavy lifting. The description only restates that an address or coordinates are accepted and does not clarify whether at least one is required or how address and coordinates interact when both 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?

States a specific verb and resource: 'Look up the OpenStreetMap place' for an address or coordinates. The scope sentence ('Planning, crime, ownership, and valuation stay unavailable') bounds what the result is not, which helps an agent separate this from richer report/analysis siblings, though no sibling is named directly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Input conditions are clear (address OR coordinates) and the explicit exclusion list tells the agent when this tool will not satisfy a planning/crime/ownership/valuation need. It stops short of naming the alternative tools for those needs, so routing is implied rather than prescribed.

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