Skip to main content
Glama
Sign In

mouseedge-skipper

by com.mouseedge
OverviewDiscussionsAdmin

scan_resort_room_windows

Read-only

Scan sliding consecutive night windows for a target Disney resort (e.g. find 4 consecutive nights at Disney's Riviera Resort between Oct 10 and Oct 18, checking all candidate sliding windows). Returns exact room type, package name, nightly rate, total stay price, tax, and direct booking links.

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

Input Schema

NameRequiredDescriptionDefault
adultsNoNumber of adults (default: 2).
nightsNoNumber of consecutive nights needed (e.g. 4 or 5, default: 4).
resortNoTarget Disney resort name, slug, or ID (e.g. "riviera", "grand floridian", "18995875"). Defaults to "riviera".
endDateNoLatest departure date in YYYY-MM-DD format (e.g. "2026-10-18"). Optional; defaults to 22 days out.
childrenNoNumber of children (default: 0).
startDateNoEarliest arrival date in YYYY-MM-DD format (e.g. "2026-10-10"). Optional; defaults to 14 days out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / endDate / description
      Previous value: -"Latest departure date in YYYY-MM-DD format (e.g. \"2026-10-18\")."New value: +"Latest departure date in YYYY-MM-DD format (e.g. \"2026-10-18\"). Optional; defaults to 22 days out."
    • changedInput schema / properties / nights / description
      Previous value: -"Number of consecutive nights needed (e.g. 4 or 5)."New value: +"Number of consecutive nights needed (e.g. 4 or 5, default: 4)."
    • changedInput schema / properties / resort / description
      Previous value: -"Target Disney resort name, slug, or ID (e.g. \"riviera\", \"grand floridian\", \"18995875\")."New value: +"Target Disney resort name, slug, or ID (e.g. \"riviera\", \"grand floridian\", \"18995875\"). Defaults to \"riviera\"."
    • changedInput schema / properties / startDate / description
      Previous value: -"Earliest arrival date in YYYY-MM-DD format (e.g. \"2026-10-10\")."New value: +"Earliest arrival date in YYYY-MM-DD format (e.g. \"2026-10-10\"). Optional; defaults to 14 days out."
    • removedInput schema / required
      Removed value: -[
-  "resort",
-  "nights",
-  "startDate",
-  "endDate"
-]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

readOnlyHint=true is consistent with a scan, so no contradiction. Beyond annotations, the description adds real value by enumerating what comes back (room type, package name, nightly rate, total stay price, tax, direct booking links) — notable because there is no output schema — and by clarifying that all candidate sliding windows are checked, which explains the cost/multiplicity of the operation. It stops short of stating how many windows or requests are issued for a wide date range.

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?

Two sentences: the first front-loads the operation and its semantics, the second packages the return fields. Little waste, though the parenthetical example is somewhat long and the return-field list could be tighter.

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 six optional parameters, no output schema, and no nested objects, the description covers purpose, mechanism (sliding windows), and returns, which is enough for an agent to invoke it correctly. Remaining gaps — expected runtime/request volume for wide ranges and the choice against the availability sibling — are modest but real.

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 every parameter is already documented with type, default, and example. The description reinforces the date-range and night-count semantics through its example but adds no format or edge-case detail (e.g. what happens if the range is shorter than 'nights', or how defaults 14/22 days interact). Baseline 3 is appropriate.

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 names a specific verb and resource ('Scan sliding consecutive night windows for a target Disney resort') and grounds it with a concrete example ('4 consecutive nights at Disney's Riviera Resort between Oct 10 and Oct 18'). It does not, however, distinguish itself from the sibling 'get_resort_hotel_availability', which an agent could plausibly confuse with this one when a specific date range is already known.

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 demonstrated by example rather than stated as a rule: the agent can infer this is the right tool when it needs N consecutive nights somewhere inside a date range. There is no explicit when-not guidance, no mention of when the date-range based sibling should be used instead, and no note on whether watch/alert tools should be paired with this scan.

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