Skip to main content
Glama

BRAINIAC Property Intelligence

Extract amenities

property-intelligence_amenities-extract
Read-onlyIdempotent

Keep amenities printed in the description separate from amenities copied from the request. Caller amenities are not checked against the property. Price $0.03 USDC. POST /api/v1/property-intelligence/amenities-extract. 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_amenities-extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
amenitiesNoamenities, array. Optional.
descriptionNodescription, string, length 1 to 20000. Optional.

Output Schema

NameRequiredDescriptionDefault
findingsNofindings. Array.
amenitiesNoamenities. Array.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
officialValuationNoofficialValuation. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly/openWorld/idempotent/non-destructive), the description discloses the price ($0.03 USDC), the HTTP endpoint, and crucially that an unpaid call returns x402 payment terms without executing. That payment gating is the kind of behavioral detail an agent would otherwise get wrong; the only minor gap is that POST is never reconciled with the read-only annotation.

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 the core purpose followed by cost and payment mechanics. Little waste, though the opening sentence's phrasing is slightly indirect and could be tightened into a plain 'Extract...' statement.

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?

For a two-parameter, read-only extraction tool with a full input schema and an output schema, the definition covers purpose, cost, and payment failure behavior adequately. It leaves only minor ambiguity about calling with neither parameter supplied, since both are optional.

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 baseline is 3. The description does add semantic meaning by explaining that one input holds amenities already supplied by the request and the other holds the free-text description to scan, but it does not clarify what happens when either optional parameter is omitted.

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 concrete operation on a concrete resource: separating amenities found in the property description from amenities supplied by the caller. That scope distinguishes it from a generic extractor, though the verb 'keep ... separate' is slightly awkward and does not explicitly contrast with any named sibling.

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 only implied through the two-source framing (description vs. request amenities), and a useful boundary is stated: caller amenities are not checked against the property. There is no explicit when-to-use versus when-not guidance and no named alternative tool for related analysis such as description-analyze or listing-extract.

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