Skip to main content
Glama

Nomad Stays

by io.github.nomadstays
OverviewDiscussionsAdmin

uploadStayPhoto

Upload a photo to one of your Stay's photo areas. Supply EXACTLY ONE of 'url' (a public https:// link, e.g. a Google Drive or Dropbox share link — the server downloads it) or 'base64' (the raw image bytes, base64-encoded — use this when you already have the image data in hand, e.g. a user attached a photo in the conversation, and have nowhere public to host it first). The photo is validated against the same minimum specs as a manual upload: JPEG, PNG, or WebP, under 20MB, and a minimum resolution that depends on area. Most areas require at least 1920x1080 landscape; 'host' requires at least 1080x1350 PORTRAIT — a landscape photo will be rejected for that area. Every upload is downscaled to fit within 2560x1440 and re-encoded server-side as WebP (stripping metadata and anything that isn't genuine image data) before storage. Requires NOMADSTAYS_MCP_AGENT_TOKEN.

Input Schema

NameRequiredDescriptionDefault
urlNoA public https:// URL the server can download the image from (e.g. a Google Drive or Dropbox share link). Supply this OR base64, not both.
areaYesWhich photo area this belongs to: - 'listing': general Stay gallery photos (multiple allowed, min 1920x1080 landscape) - 'main': the single hero/cover photo shown first for the Stay (min 1920x1080 landscape, replaces any existing main photo) - 'workspace': coworking/workspace photos for the whole Stay (multiple allowed, min 1920x1080 landscape) - 'host': a photo of the HOST/CONTACT PERSON, not the property — must be PORTRAIT orientation, min 1080x1350 (replaces any existing host photo) - 'room': photos for one specific room — requires roomId (multiple allowed, min 1920x1080 landscape)
base64NoBase64-encoded JPEG, PNG, or WebP image bytes (a data:image/...;base64,... URI prefix is also accepted and stripped automatically). Supply this OR url, not both. Under ~27MB encoded (20MB image).
roomIdNoRequired when area is 'room' — the room's EntryID (use getMyStayRooms to find it). Ignored for other areas.
stayIdYesThe Stay's EntryID (use getMyStays to find it)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Far exceeds the annotations: it discloses server-side download of the URL, per-area resolution/orientation validation rules (host must be PORTRAIT), the 20MB cap, mandatory downscaling to 2560x1440, WebP re-encoding, metadata stripping, the NOMADSTAYS_MCP_AGENT_TOKEN requirement, and that 'main'/'host' overwrite existing photos. The last point is the only mild tension with destructiveHint=false, but it is disclosed rather than hidden.

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-loads the core action and the source-parameter rule before the lengthy validation details; the nested parentheticals are dense but each carries actionable constraint information. Slightly long, but no sentence is filler.

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?

No output schema exists, yet the description never says what comes back (e.g. a new photo ID or confirmation), which is the one gap for an agent that may want to reference the uploaded photo later. Otherwise it covers prerequisites, constraints, and side effects thoroughly for a 5-parameter mutation.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning on top: the EXACTLY-ONE exclusivity of url/base64, the fact that the server fetches the URL itself, and the orientation constraint that makes 'host' reject landscape images. Only the resolution thresholds are duplicated rather than extended.

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?

States a specific verb+resource ('Upload a photo to one of your Stay's photo areas') with the scoping unit ('photo area') that separates it from getMyStayPhotos, deleteStayPhoto, and reorderStayPhotos. The description makes clear this creates/attaches an image rather than reading or reordering one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit decision rules for the mutually exclusive source parameters: use 'url' when the image is publicly hosted, 'base64' when the agent already holds the bytes. It also states the roomId precondition for the 'room' area. It never names a sibling tool as an alternative or exclusion, so it stops just short of 5.

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

All Nomad Stays 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