Skip to main content
Glama

Neofort IMO — ansambluri rezidențiale București

Search available apartments

search_apartments
Read-onlyIdempotent

Search AVAILABLE apartments across Neofort IMO residential projects in Bucharest. Filters: rooms, max price (EUR, excl. VAT), min area, zone/sector, stage, promotions only. Results are sorted by price ascending and include every price option shown on the website (e.g. by down-payment level). All prices are in EUR and EXCLUDE 21% VAT.

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

Input Schema

NameRequiredDescriptionDefault
zoneNoArea or sector, e.g. "Titan", "Colentina", "Sector 3", "Militari".
limitNoMax results (default 20).
roomsNoNumber of rooms (1 = studio/garsonieră; 4 means 4 or more).
stageNofinalizat = ready to move in; in_constructie = under construction.
promo_onlyNoOnly apartments with an active promotion.
min_area_sqmNoMinimum usable area in square metres.
max_price_eurNoMaximum price in EUR, excluding VAT.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real context the annotations cannot carry: results are price-ascending, all price options per listing are returned (e.g. by down-payment level), and all figures are EUR excluding 21% VAT.

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?

Four dense sentences, front-loaded with what is searched before filters and result semantics. The VAT warning is placed last where it is hardest to miss, and there is no filler.

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?

No output schema exists, and the description compensates by describing result ordering and price composition, which is the main thing an agent needs to interpret the response. It is complete for a zero-required-parameter search tool, with only minor gaps around how paging/limit behaves when results are truncated.

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 rooms, stage enum, zone, min_area_sqm and max_price_eur are already fully documented, giving a baseline of 3. The description restates the price filters and VAT exclusion but adds no syntax or semantics beyond the schema, and does not clarify how max_price interacts with the multiple price options it says are returned.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ("Search AVAILABLE apartments") and constrains it to a named domain (Neofort IMO residential projects in Bucharest), with the capitalized AVAILABLE signalling the scope boundary. It also enumerates the filter axes, so an agent can map an apartment-hunting request onto this tool without reading the schema first.

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 domain and filters, but there is no explicit when-to-use/when-not guidance and no routing to alternatives such as get_project or list_projects for project-level information. An agent must infer that this is the listing-search entry point rather than being told.

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