Skip to main content
Glama

emailMeShortlist

Emails the person a one-off shortlist of up to 5 stays they have been looking at, with member prices, and a link to create a free account. Members save around 5% - create an account today while it's free. Use it when the person has no account yet and would like to keep or come back to these stays, or says they'll decide later. ONLY call it after the person has asked for the email to be sent to them and given you their address; set userConsented to true to confirm that. It sends one email per address (repeat requests are ignored), never marketing, and carries an opt-out link. Prices and links are looked up by Nomad Stays, not taken from you. The reply is always the same whether or not an email is sent.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "email": "<email>",
      "stayIds": "<stayIds>",
      "userConsented": "<userConsented>"
    },
    "name": "emailMeShortlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe person's own email address, given to you by them for this purpose
stayIdsYesStay ids (EntryId from the stay search tools) for the stays to include, best match first. Maximum 5.
userConsentedYesSet to true only if the person explicitly asked for this shortlist to be emailed to this address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations mark this as a non-read-only, non-destructive write with no external-world hint; the description adds substantial context beyond that: one email per address, repeats ignored, never marketing, opt-out link included, and a deliberately uniform reply whether or not a send occurs. It does not spell out rate limits or failure modes, but the meaningful behavioral traits are covered.

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-loaded with the core action and the critical consent gate, and generally every sentence provides agent-relevant information. The embedded promotional line ('Members save around 5% - create an account today while it's free') is marketing copy that adds little for the calling agent and slightly dilutes the signal.

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 3-parameter tool with full schema coverage and no output schema, the description covers preconditions, side effects, idempotency, and the invariant reply shape. The only gap is the absence of failure-mode guidance, which is minor here because the reply is stated to be uniform.

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; the description adds real meaning by clarifying that prices and links are resolved server-side rather than passed in, and by tying userConsented to the explicit consent precondition. It reinforces rather than merely repeats the schema.

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 with scope: emails a one-off shortlist of up to 5 stays at member prices with an account-creation link. An agent can immediately tell this apart from booking or application siblings, and the 'one-off' scope is 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 explicit when-to-use conditions (no account yet, wants to revisit these stays, or will decide later) and a hard precondition (ONLY after the person asked and supplied their address, with userConsented=true). The constraint is front-loaded and unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.