Skip to main content
Glama
BACH-AI-Tools

Idealista7 MCP Server

list_offices

Find office properties for sale or rent using filters such as location, price range, size, layout type, and amenities like elevator, heating, or air conditioning.

Instructions

List office properties with the requested parameters. Buy/Rent \u003e Offices. Filters are optional parameters, please make sure the request follows the rules in each parameter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderYesExample value:
garageNoExample value:
layoutNoDistribution parameter. Pick between: Indifferent: leave blank (default) Open plan: openPlan Divided by walls: withWalls
localeYesExample value:
hasPlanNoExample value:
heatingNoExample value:
maxSizeNoExample value: 0
minSizeNoExample value: 0
numPageYesExample value: 11
elevatorNoExample value:
exteriorNoExample value:
hotWaterNoExample value:
locationYesExample value:
maxItemsYesExample value:
maxPriceNoExample value: 0
minPriceNoExample value: 0
securityNoExample value:
bankOfferNoBank-owned
operationYesSearch sales or rentals. Pick between: sale|rent
sinceDateNoPublication Date Parameter. One of the following values. Indifferent: leave blank (by default) | Last 24h: T (Rent operation only) | Last 48h: Y (Buy operation only) | Last week: W | Last month: M
accessibleNoExample value:
locationIdYesExample value: 0-EU-ES-28-07-001-079
buildingTypeNoType of building parameter. Pick between: Indifferent: leave blank (default) Exclusively for offices: exclusive Mixted use: mixed
locationNameYesExample value: Madrid
airConditioningNoExample value:
Behavior3/5

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

No annotations are provided, so the description carries the burden. It states 'List' implying read-only, but does not explicit state non-destructiveness or confirm no side effects. The warning to follow parameter rules adds some context but not behavioral depth.

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?

Two sentences, straight to the point: purpose and a caution. Could include more detail without being too long, but it's efficient and front-loaded.

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

Completeness2/5

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

Given the complexity (25 parameters, 8 required) and lack of output schema/annotations, the description fails to explain output format, pagination, or sorting. It leaves too much to the agent's inference.

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

Parameters2/5

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

While schema description coverage is 100%, most are minimal ('Example value: ') adding no real meaning. The description only generically warns to follow parameter rules without clarifying specific parameter semantics beyond what the schema provides.

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?

The description clearly states the verb 'List' and resource 'office properties', and specifies the category 'Buy/Rent > Offices'. This precisely distinguishes it from sibling tools like list_buildings or list_commercial_properties.

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?

The description mentions filters are optional and advises to follow parameter rules, but provides no guidance on when to use this tool versus alternatives (e.g., list_commercial_properties). Implied usage is for office listings only.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BACH-AI-Tools/idealista7'

If you have feedback or need assistance with the MCP directory API, please join our Discord server