Skip to main content
Glama

search_listings

Read-only

How many listings match, and 24 of them (price, bedrooms, area, city, url). Use offset to get the next 24. count_capped true means more than count match.

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": "search_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
bboxNowest,south,east,north; ignored when areas are set
sortNonewest
areasNodeelgemeente codes like "24104A"; a bare municipality NIS selects all of it
limitNo
placeNoa place name like "Gent" or "Ixelles": the deelgemeente of that name, never a whole municipality; adds to `areas`
offsetNo
min_sqmNominimum habitable area, m2
sourcesNoagency domains
featuresNoevery one the ad says the home has, such as pool or sauna
price_maxNo
price_minNo
energy_labelNoworst EPC / PEB label accepted; homes with no label are left out
listing_typeNo
max_bedroomsNomost bedrooms accepted: a person who wants one or two, not five
min_bedroomsNo
property_typesNo
exclude_under_optionNoleave out the homes under option: a buyer is already signing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds genuinely useful behavior beyond that by explaining that results are paged at 24 and that count_capped=true signals the count is truncated. That truncation signal is non-obvious from any structured field and prevents an agent from misreading the total. It stops short of covering ordering defaults, empty-result behavior, or rate limits.

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 with no filler, and the return shape is front-loaded. The opening clause ('How many listings match, and 24 of them') is grammatically compressed enough that it takes a second read to parse as 'returns the match count plus 24 listings'.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 17-parameter tool with no output schema, the description covers the result payload and pagination but leaves the filtering model, sort semantics and the interaction between the stated 24-item page and the `limit` maximum unaddressed. An agent can call it, but a fair amount of important behavior must be inferred from the schema.

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 53% across 17 parameters, so roughly half the parameters carry no inline documentation. The description adds real meaning only for offset (it advances by one page of 24); the remaining filters, sort options and limit are left entirely to the schema. It also states a fixed page size of 24 while `limit` allows up to 200, which an agent must reconcile on its own.

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 conveys a specific resource and result shape: it returns a match count plus a page of listings with price, bedrooms, area, city and url. It never names the verb 'search' explicitly and gives no differentiation from the sibling get_listing, but an agent can still tell this is the list/query tool and get_listing is not.

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?

The only usage direction is 'Use `offset` to get the next 24', which covers pagination mechanics. There is no guidance on when to use this versus get_listing, no note on which filters combine (e.g. bbox ignored when areas set, though the schema says this), and no exclusions or prerequisites.

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