Skip to main content
Glama

La Palme d'Azur Cannes: hotel, aparthotel & resort

Apartment types of the residence

list_apartments
Read-onlyIdempotent

The 7 apartment types of Residence La Palme d'Azur Cannes Verrerie (studios, 1- and 2-bedroom apartments, duplexes; sea or pool view) with capacity, surface, bathrooms, air conditioning, bedding per room, multilingual names and page URLs. No prices here: call search_availability with dates. direct_only: true marks the apartments sold exclusively on the official website (the studios), which no third-party platform lists.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the description only needs to add context — which it does by explaining the `direct_only: true` marker means exclusive direct-website sale (the studios) and by warning that third-party platforms omit those. Useful non-obvious semantics rather than restatement.

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?

Front-loads scope and contents, then adds two short routing/semantics sentences with no filler. The opening sentence is dense with comma-separated attributes but every clause carries information an agent would otherwise have to discover by calling.

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 no output schema, the description is the only source on return values, and it covers the field families (capacity, surface, bathrooms, AC, bedding, names, URLs) plus the direct_only semantics and where pricing lives. Nothing essential to calling or interpreting this tool 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?

Zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It instead spends its words on return-field semantics, notably the direct_only flag, which is the right use of space for a no-arg tool.

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 resource and enumerates exactly what it returns: the 7 apartment types with capacity, surface, bathrooms, air conditioning, bedding per room, multilingual names and page URLs. An agent knows instantly this is the catalogue of unit types rather than availability or booking data.

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

Usage Guidelines4/5

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

Explicitly states a when-not ('No prices here: call search_availability with dates'), which routes the agent to the correct sibling for pricing. It does not distinguish itself from get_property_facts (residence-level facts), leaving mild ambiguity about which to call first, but the primary exclusion is clear.

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