Skip to main content
Glama

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

Verified property facts

get_property_facts
Read-onlyIdempotent

Verified facts about Residence La Palme d'Azur Cannes Verrerie read from its database: name, address, phone, GPS, check-in and check-out times, security deposit, pets policy, parking, pools and their season, on-site services, distances to the beach, the Palais des Festivals, stations and the airport, spoken languages, Google rating. Use it for practical questions. It contains no prices: call search_availability for a quote.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the data is verified and database-sourced, and a hard scope boundary (no pricing data) is disclosed. It stops short of describing response shape or freshness/staleness of the facts, which would be the remaining useful detail.

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-loaded with the core claim, then the content inventory, then the pricing exclusion and redirect — a sensible order with no filler sentences. The long mid-sentence list of facts is dense but each item tells the agent a question it can answer, so the length is largely earned.

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?

With no output schema and no parameters, the description carries the burden of describing return content and does so thoroughly via the field inventory. It is nearly complete; only the form of the response (single structured object, sections, units/formats for times and distances) is left unstated.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter meaning to add. The field enumeration in the description serves as return-value information rather than parameter documentation, which is appropriate but does not raise the score.

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 names a specific verb and resource — verified facts about one named property read from its database — and enumerates the exact content domains (address, GPS, check-in/out, deposit, pets, parking, pools, distances, languages, rating). An agent can immediately tell this apart from search_availability or list_apartments without opening anything else.

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?

It states the use case ('practical questions') and an explicit exclusion with a named redirect ('It contains no prices: call search_availability for a quote'). That is the when-to-use, when-not-to-use, and the alternative, all in one sentence.

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