Snapstay

Create a guest profile with a name, email, and optional phone and billing address

guests.create

Create a guest profile with a name, email, and optional phone and billing address. Returns the guest ID and name. Each successful call creates a separate profile, including calls with the same email. Use guests.list to find existing profiles.

Input Schema

Name	Required	Description
`email`	Yes	Guest email address, such as jordan@example.com.
`phone`	No	Contact phone number, including the country calling code.
`givenName`	Yes	Guest given name, from 1 to 100 characters.
`familyName`	Yes	Guest family name, from 1 to 100 characters.
`billingAddress`	No	Optional guest billing address.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 23, 2026

addedInput schema / examples

Added value: +[
+  {
+    "email": "jordan@example.com",
+    "familyName": "Sample",
+    "givenName": "Jordan"
+  }
+]

changedInput schema / properties / billingAddress / description

Previous value: -"Guest billing address."New value: +"Optional guest billing address."

changedInput schema / properties / email / description

Previous value: -"Contact email address."New value: +"Guest email address, such as jordan@example.com."

Changed14 schema fields changedOct 18, 2026
- addedInput schema / properties / billingAddress / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / billingAddress / description
```
Added value: +"Guest billing address."
```
- addedInput schema / properties / billingAddress / properties / city / description
```
Added value: +"City or town."
```
- addedInput schema / properties / billingAddress / properties / country / description
```
Added value: +"Two-letter country code, such as GB."
```
- addedInput schema / properties / billingAddress / properties / postcode / description
```
Added value: +"Postal code. Omit when not applicable."
```
- addedInput schema / properties / billingAddress / properties / region / description
```
Added value: +"State or region. Omit when not applicable."
```
- addedInput schema / properties / billingAddress / properties / street / description
```
Added value: +"Street address."
```
- addedInput schema / properties / email / description
```
Added value: +"Contact email address."
```
- addedInput schema / properties / familyName / description
```
Added value: +"Guest family name, from 1 to 100 characters."
```
- addedInput schema / properties / givenName / description
```
Added value: +"Guest given name, from 1 to 100 characters."
```
- addedInput schema / properties / phone / description
```
Added value: +"Contact phone number, including the country calling code."
```
- addedInput schema / properties / phone / minLength
```
Added value: +1
```
- removedInput schema / properties / phone / properties
```
Removed value: -{
-  "country": {
-    "type": "string"
-  },
-  "number": {
-    "type": "string"
-  }
-}
```
- changedInput schema / properties / phone / type
```
Previous value: -"object"New value: +"string"
```
First observedOct 17, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=false, but the description makes that non-idempotency concrete and operational: each call creates a distinct profile even for a duplicate email. It also names the return payload (guest ID and name), which an agent needs for chaining. No permission, validation-error, or rate-limit context, so not a 5.

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?

Four short sentences in priority order: what it does, what it returns, the duplicate-profile behavior, then the alternative. Nothing is repeated from the title and no sentence is filler.

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

Completeness5/5

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

For a simple create tool with full schema documentation, an output schema, and clear annotations, the description covers everything an agent needs: purpose, return value, the duplicate-creation trap, and the routing to guests.list.

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%, so all five parameters and the nested billing address are already documented with constraints. The description only restates the field set and is slightly looser than the schema, saying 'a name' where givenName and familyName are both required. Baseline 3 for full schema coverage with no added parameter detail.

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 and resource ('Create a guest profile') plus the payload contents, which immediately separates it from read-side siblings like guests.search and guests.bookings. The closing pointer to guests.list makes the create-vs-find boundary explicit.

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

Usage Guidelines5/5

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

Gives both when-to-use ('Create a guest profile...') and a concrete alternative with its condition ('Use guests.list to find existing profiles'). The warning that repeated calls with the same email produce separate profiles tells the agent not to reach for this tool to deduplicate or upsert.

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

All Snapstay tools Inspect

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

Need Help?