Skip to main content
Glama

Resident reviews of a building by address

search_address
Read-only

Look up a residential building (apartment block, house, residential complex) by its address and get the reviews of people who lived there: ratings 1-5 and their words about noise, damp, heating, water, the landlord or the management. Use before renting or buying a home at an address, in any country.

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": {
      "query": "<query>"
    },
    "name": "search_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesStreet, house number and city, any language

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description goes beyond that by spelling out the payload shape (numeric ratings plus free-text complaints across specific building-quality topics), which tells the agent what evidence it will actually get. It does not cover empty-result behavior or whether reviews span all time, so it falls short of full disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two sentences, both front-loaded with the resource and the action, and the second one supplies usage context. There is no filler, and the value proposition (ratings plus resident commentary) comes before the advisory usage note.

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?

There is no output schema, so the description carries the burden of describing returns, and it does so concretely with rating range and review topics. For a single-parameter read tool this is nearly complete; only edge-case behavior (address not found, no reviews available) is left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage on a single parameter, the baseline is 3, and the description earns an extra point by clarifying that the query is a residential building address and enumerating the building types it can denote (apartment block, house, residential complex). The multi-language and any-country scope adds useful meaning beyond "Street, house number and city."

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+resource pair: look up a residential building by address and return its residents' reviews, plus the exact data returned (1-5 ratings, comments on noise, damp, heating, water, landlord, management). It is clear and unambiguous, though it never names or distinguishes itself from the sibling latest_reviews, so the boundary is inferred only from the address-vs-recency framing.

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?

"Use before renting or buying a home at an address, in any country" gives a concrete decision context and geographic scope. There are no explicit exclusions or named alternatives, so an agent is not told when to prefer latest_reviews instead, but the when-to-use condition is clear.

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