Skip to main content
Glama

BRAINIAC Property Intelligence

Analyze a listing description

property-intelligence_description-analyze
Read-onlyIdempotent

List bedrooms, area, amenities, and marketing phrases only where those words are printed. Marketing words are not a quality score. Price $0.03 USDC. POST /api/v1/property-intelligence/description-analyze. An unpaid call returns the x402 payment terms and does not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "description": "<description>"
    },
    "name": "property-intelligence_description-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
descriptionYesdescription, string, length 1 to 20000. Required.

Output Schema

NameRequiredDescriptionDefault
bedroomsNobedrooms. Number.
findingsNofindings. Array.
amenitiesNoamenities. Array.
bathroomsNobathrooms. Number.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
floorAreaSqmNofloorAreaSqm. Number.
marketingPhrasesNomarketingPhrases. Array.
officialValuationNoofficialValuation. Boolean.

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 readOnly/idempotent annotations, it discloses cost ($0.03 USDC), the payment gate (an unpaid call returns x402 terms and does not run), and an interpretive caveat that marketing words are not a quality score. Those are meaningful operational and semantic facts an agent could not get from annotations, though the response shape is left to the output schema.

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?

Sentences are short and front-loaded: extraction targets first, then the interpretive caveat, then price, endpoint, and payment behavior. Slightly telegraphic phrasing, but nothing is padded or redundant.

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 one simple parameter, full annotations, and an output schema, the description covers the pieces an agent needs that structured fields do not: cost, payment gating, and the extraction caveat. Only cross-tool routing guidance is missing.

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% and there is a single required string parameter, so the schema already carries the semantics. The description adds only indirect meaning by enumerating what is extracted from that string, which is a reasonable baseline-3 contribution.

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 names the concrete outputs (bedrooms, area, amenities, marketing phrases) so the agent knows this reads a listing description and pulls structured facts plus marketing language. It does not contrast itself with near neighbors such as amenities-extract or listing-extract, so differentiation rests on the title and name alone.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative among the many sibling extraction tools. The only directional cue is the constraint to extract 'only where those words are printed', which shapes behavior rather than tool selection.

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