Skip to main content
Glama

Get one Flatio listing

flatio_get_listing
Read-only

Use this when someone asks about one listing whose id flatio_search_listings returned: its description, amenities, house rules, stay limits, availability, rating and price. With move_in and move_out it prices exactly those dates, broken into rent, service fee and deposit, and without them it gives the monthly rent. Not for finding listings. Give the guest each listing's url exactly as returned, with all its query parameters.

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": {
      "id": "<id>"
    },
    "name": "flatio_get_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesListing id from flatio_search_listings, e.g. 95507.
move_inNoMove-in date as YYYY-MM-DD, e.g. "2027-02-01". Send together with move_out.
currencyNoCurrency of every price in the result, e.g. "EUR". Send the currency of the search the id came from. Defaults to the currency of the response language's Flatio site.
languageNoLanguage of titles, texts and links, e.g. "en", "cs", "de", "es", "pt". Defaults to the language the client reports, else English.
move_outNoMove-out date as YYYY-MM-DD, after move_in, e.g. "2027-08-01".

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
cityNo
priceYes
titleYes
guestsYes
photosYes
ratingNo
bedroomsNo
categoryNo
districtNo
amenitiesYes
bathroomsNo
descriptionYes
house_rulesYes
availabilityYes
review_countYes
floor_size_m2No
max_stay_daysNo
min_stay_daysYes
property_typeYes
available_fromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare a read-only, non-destructive, closed-world read, so the safety profile needs no restating. The description adds behavior the annotations cannot carry: with move_in and move_out it prices exactly those dates broken into rent, service fee and deposit, and without them it returns monthly rent. It also imposes a client-facing rule (pass the listing's url through verbatim with all query parameters), which is genuinely useful behavioral context.

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?

Four tight sentences, front-loaded with the use trigger and return payload before the pricing-mode detail. Slightly dense – three distinct ideas (content, pricing modes, url passthrough) packed into two sentences – but nothing is wasted or redundant with the schema.

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

Completeness5/5

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

With an output schema handling return shape and annotations handling safety, the description fills the remaining gaps: what content comes back, how the two pricing modes differ, and the url passthrough requirement. Nothing an agent needs to invoke or relay results correctly is missing.

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?

Schema description coverage is 100%, so the baseline would be 3; the description earns more by explaining the date-pair semantics that the schema only hints at – both dates together price a specific stay, omitting them falls back to monthly rent. It does not restate currency or language defaults, which the schema already covers.

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?

States a specific verb and resource (fetch one listing by id) and enumerates exactly what it returns: description, amenities, house rules, stay limits, availability, rating and price. It also explicitly rules out the sibling's job with "Not for finding listings", so an agent can separate it from flatio_search_listings without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ("Use this when someone asks about one listing whose id flatio_search_listings returned") and an explicit exclusion ("Not for finding listings"), which together route the agent correctly between discovery and detail. The id-provenance requirement is also stated, so the caller knows the id must come from a prior search.

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