Skip to main content
Glama

BRAINIAC Property Intelligence

List nearby location features

property-intelligence_location-features
Read-onlyIdempotent

List schools, hospitals, pharmacies, supermarkets, stations, and parks that OpenStreetMap places within 500 metres. A missing feature is not treated as absent. Price $0.05 USDC. POST /api/v1/property-intelligence/location-features. 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_location-features"
  }
}

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
statusNostatus. String.
featuresNofeatures. Array.
findingsNofindings. Array.
latitudeNolatitude. Number.
checkedAtNocheckedAt. String.
longitudeNolongitude. Number.
limitationsNolimitations. Array.
officialValuationNoofficialValuation. Boolean.

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 read-only, idempotent, open-world and non-destructive, so the safety profile is covered. Beyond that the description adds genuinely useful behavior: a fixed 500 m radius, an OSM data source, the caveat that absent features are not proof of absence, a $0.05 USDC cost, and the x402 payment failure mode where an unpaid call returns terms and does not execute. The only shortfall is that it does not say what a paid-but-failed call 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded with the capability and scope, then the data caveat, then cost and transport details. Every sentence carries operational weight, including the endpoint path and payment behavior. Slightly terse phrasing ("A missing feature is not treated as absent") costs a moment of parsing but nothing is padded.

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-value documentation is not required here. The description covers scope, data source, cost, the payment gate and the data-completeness caveat, which is what an agent needs to call this correctly and interpret an empty result. The only residual gap, how address versus coordinates are resolved, is minor against the schema's full coverage.

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 address, latitude and longitude are already documented with types and ranges, which sets the baseline at 3. The description adds the 500 m proximity concept but never clarifies the relationship between the address and coordinate inputs, notably that all three are optional and that some locator must presumably be supplied. That is the one semantic point the schema cannot convey.

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 ("List") plus an enumerated resource set (schools, hospitals, pharmacies, supermarkets, stations, parks) and bounds it to a 500 m radius sourced from OpenStreetMap. That is far more concrete than the title alone. It does not, however, distinguish this tool from plausible siblings such as amenities-extract or area-context, so the agent must infer the boundary.

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 enumerated categories and the 500 m radius, which tells an agent the rough situation this fits. There is no explicit when-to-use versus when-not-to-use statement and no named alternative for the overlapping proximity/amenity tasks. The payment sentence is a precondition, not usage guidance.

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