Skip to main content
Glama
Sign In

mouseedge-skipper

by com.mouseedge
OverviewDiscussionsAdmin

get_resort_hotel_availability

Read-only

Check real-time Disney World resort hotel room availability, categories, and nightly rates across all 35 Disney resorts (e.g. Disney's Riviera Resort, Grand Floridian, Polynesian, Contemporary, Beach Club, Yacht Club, BoardWalk, Animal Kingdom Lodge, Caribbean Beach, Pop Century, Art of Animation).

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_resort_hotel_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
adultsNoNumber of adults (default: 2).
resortNoOptional Disney resort name or slug (e.g., "riviera", "grand floridian", "polynesian", "contemporary"). Omit to check all 35 resorts.
childrenNoNumber of children (default: 0).
checkInDateNoArrival date in YYYY-MM-DD format (e.g., "2026-11-15"). Optional; defaults to 14 days out if omitted.
checkOutDateNoDeparture date in YYYY-MM-DD format (e.g., "2026-11-19"). Optional; defaults to 4 nights after check-in if omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / checkInDate / description
      Previous value: -"Arrival date in YYYY-MM-DD format (e.g., \"2026-11-15\")."New value: +"Arrival date in YYYY-MM-DD format (e.g., \"2026-11-15\"). Optional; defaults to 14 days out if omitted."
    • changedInput schema / properties / checkOutDate / description
      Previous value: -"Departure date in YYYY-MM-DD format (e.g., \"2026-11-19\")."New value: +"Departure date in YYYY-MM-DD format (e.g., \"2026-11-19\"). Optional; defaults to 4 nights after check-in if omitted."
    • removedInput schema / required
      Removed value: -[
-  "checkInDate",
-  "checkOutDate"
-]
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint annotation establishes that the operation is non-mutating, and the description consistently adds real-time behavior and the types of information inspected. It does not disclose further operational context such as the data source, freshness limitations, or behavior when no rooms are available.

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?

The single sentence front-loads the action, resource, returned information, and scope, making it easy to understand. The long parenthetical list of example resorts is more than necessary and slightly reduces conciseness.

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?

For a read operation with five optional parameters, the description and fully documented schema provide enough scope, result content, and defaults to invoke the tool correctly. Explicit sibling differentiation and brief operational caveats would improve completeness, particularly because there is no output schema.

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 coverage is 100%, with the schema already documenting date formats, defaults, party size, and the effect of omitting resort, so the baseline score applies. The description's resort examples and all-35-resorts scope reinforce that information but add no meaningful parameter syntax or interaction details.

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 clearly states the action and resource: checking Disney World resort hotel availability, room categories, and nightly rates, with an all-35-resorts scope. It does not explicitly differentiate this availability check from the potentially overlapping sibling scan_resort_room_windows.

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 wording implies use for a current hotel availability and rate check, including broad searches across resorts. It provides no explicit guidance on when to prefer this tool over scan_resort_room_windows or other siblings, leaving that selection to inference.

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

All mouseedge-skipper toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources