Skip to main content
Glama

White Sands Residences

Check villa availability

check_availability

Checks live availability of Villa Nautilus 222 for the requested arrival and departure dates.

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": {
      "arrival": "<arrival>",
      "departure": "<departure>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
arrivalYesArrival date in YYYY-MM-DD format.
departureYesDeparture date in YYYY-MM-DD format.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It adds the useful detail that availability is "live," but it does not state whether the check is read-only, whether it holds or reserves inventory, what the response contains, or any rate-limit or permission behavior.

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?

The description is a single, front-loaded sentence with no wasted wording. It immediately communicates the resource, the action, and the relevant input scope.

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

Completeness3/5

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

For a simple two-parameter availability check, the description covers the core purpose and date inputs. However, because there is no output schema or annotations, it could do more to explain what "availability" returns and whether any side effects or constraints apply.

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 both arrival and departure are already documented with date format and meaning. The description repeats the requested date range without adding new semantics or constraints beyond what the schema provides.

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

Purpose4/5

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

The description states a specific verb and resource: checking live availability for Villa Nautilus 222 across requested arrival and departure dates. This is clearly distinguishable from siblings like get_price_quote and get_booking_link, though it does not explicitly call out the distinction.

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 wording: an agent can infer it should use this tool when it needs date-specific availability. However, there is no explicit guidance about when to use this versus get_price_quote or get_booking_link, and no prerequisites or exclusions are stated.

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