Skip to main content
Glama

Ingatlankeresés

search_real_estate
Read-onlyIdempotent

Keresés a Kódvéna Ingatlan hirdetései között (eladó/kiadó, típus, település, maximális ár). Linkeket ad az adatlapokra.

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_real_estate"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoKulcsszó, pl. erkély, kert (nem kötelező)
dealNoEladó vagy kiadó (nem kötelező)
typeNoIngatlantípus (nem kötelező)
placeNoTelepülés vagy budapesti kerület, pl. Debrecen, Budapest XIII. kerület (nem kötelező)
max_priceNoLegfeljebb ennyi forint (nem kötelező)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld=false/idempotent/non-destructive, so safety is covered. The description adds genuinely new context by stating the return shape (links to the listing detail pages), which matters because there is no output schema. It omits result limits, ordering, and whether an empty result is possible, so not a 5.

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?

A single tight sentence that front-loads the verb, resource, and catalog name, then packs the filters into a parenthetical. Nothing is redundant, though the compressed parenthetical form makes it slightly dense rather than maximally scannable.

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 simple all-optional search with 100% schema coverage and full annotation coverage, the description supplies the one thing structured fields don't: the return format (links to listing pages). Only minor operational details (pagination, default result count) are absent, which is acceptable at this complexity.

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% and both enums are documented in the schema, so the baseline of 3 applies. The description merely restates the same filter dimensions (deal, type, place, max price) without adding format, matching, or precision semantics beyond what the schema already says.

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?

Specific verb + resource + scope: searching within 'Kódvéna Ingatlan' listings, with the filter dimensions enumerated (sale/rent, type, settlement, max price). This is more specific than a generic search and distinguishes it from the many other 'search*' siblings by naming the source catalog. It doesn't explicitly name an alternative tool, but the resource is unambiguous.

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 listed filter criteria and by the parenthetical noting filters are optional ('nem kötelező'), but there is no explicit statement of when to use this versus another search tool and no exclusions or prerequisites. An agent can infer intent but must guess at boundaries.

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