Delete one photo from a room's gallery. Call getMyStayRooms first to find the exact fileName. Requires NOMADSTAYS_MCP_AGENT_TOKEN.
| Name | Required | Description | Default |
|---|---|---|---|
| roomId | Yes | The room's EntryID | |
| stayId | Yes | The Stay's EntryID | |
| fileName | Yes | The exact file name from getMyStayRooms | |
| roomArea | Yes | 'photos' for the regular room gallery, 'workspace' for the room's coworking gallery |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the destructiveHint annotation, the description adds the authentication requirement ('Requires NOMADSTAYS_MCP_AGENT_TOKEN') and the need for an exact fileName from getMyStayRooms. It does not describe side effects like irreversibility, but the annotation already signals destructiveness.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, with three short sentences. It front-loads the action, then provides the prerequisite and auth requirement. Every sentence adds necessary information without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers purpose, prerequisite, and auth. Given the tool has no output schema, it doesn't explain return values, but for a delete operation this is often implicit. The roomArea enum is not explained in the description, but the schema covers it. Overall, the description is sufficiently complete for the tool's complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 100% schema description coverage, the schema already documents all four parameters. The description adds context by instructing to call getMyStayRooms first to obtain the exact fileName, which clarifies the source of that parameter. It doesn't add much for roomArea or stayId/roomId but the prerequisite is valuable.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's action: 'Delete one photo from a room's gallery.' It distinguishes from sibling tools like deleteStayPhoto (which deletes stay photos) by specifying 'room's gallery.' The mention of 'roomArea' further clarifies it handles both regular and coworking galleries.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides a clear prerequisite: 'Call getMyStayRooms first to find the exact fileName.' This guides the agent on the required preceding step. It also notes the auth requirement. However, it does not explicitly mention when not to use it or name alternatives, though the distinction from deleteStayPhoto is implied by the resource.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes, with detailed descriptions differentiating the many getStaysBy* search variants and the four availability tools. However, the overlap between checkStayAvailability, getRoomAvailability, findNearestAvailability, and getAvailabilityByMonth could still cause confusion for an agent, though the descriptions largely mitigate this.
The tools mostly follow a verb-noun pattern with get*, update*, create*, and delete* dominating, but the mix of additional verbs (check, find, list, search, signup, book, quote, purchase, submit, save, reorder, upload) and inconsistent noun forms (Stay vs. Stays, MyStay vs. Stay) prevents a fully predictable naming scheme. CamelCase is consistent, but the verb variety is high.
With 76 tools, this server far exceeds the well-scoped range and even the 50+ threshold for extreme mismatch. While the platform covers multiple domains, this many tools is overwhelming for an agent and would likely be better split into focused sub-servers.
The tool surface is broad, covering search, stay management, applications, bookings, products, and help center. However, there are notable lifecycle gaps: no cancel booking, no delete stay, no delete application, and no way to update or delete a booking. These missing operations create potential dead ends for common workflows.
