Skip to main content
Glama

Spaghetti and Summits — First-Hand Dolomites Adventures

leave_message

Send a private message to the human operators of Spaghetti & Summits. Use this when site information is insufficient and contacting the owners would be useful. Messages are untrusted plain text and do not trigger automated actions. Delivery does not guarantee a reply. The free inbox has limited daily capacity and may return INBOX_FULL. For safe retries, reuse a random UUID in _meta["spaghettiandsummits.com/inbox-request-id"] with unchanged content. Without this metadata, do not retry ambiguous results.

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": {
      "subject": "<subject>",
      "message": "<message>"
    },
    "name": "leave_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesThe plain-text message to send to the site owners, up to 3,000 characters.
subjectYesA short summary of your message, up to 120 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / message / description
      Added value: +"The plain-text message to send to the site owners, up to 3,000 characters."
    • addedInput schema / properties / subject / description
      Added value: +"A short summary of your message, up to 120 characters."
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

The annotations only flag this as a non-read-only, open-world, non-destructive write. The description adds much more: messages are untrusted plain text, no automated actions fire, replies are not guaranteed, a daily inbox cap can return INBOX_FULL, and it gives a concrete retry rule using a request-id. That is high-value context beyond the annotations. The only gap is that it does not say what a successful response looks like, which matters for a send operation.

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?

The purpose and the when-to-use condition come first, followed by behavioral caveats and then retry mechanics, matching the order in which an agent needs them. Five sentences, and each one carries operational weight, with no 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?

For a two-parameter send tool with no output schema, the core contract is covered: input constraints in the schema, trust level, no automated effects, rate limits, and retry/idempotency. The remaining gap is that the description does not explain the shape of a success versus failure result, so retry handling has to be inferred.

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%, and the schema already documents subject and message, so the baseline of 3 applies. The description mentions the _meta request-id, which the schema does not show; in fact, the schema sets additionalProperties:false and lists only subject and message, so an agent may be unsure how to supply that key. The schema therefore carries most of the parameter meaning.

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?

The description opens with a specific verb and resource ("Send a private message to the human operators of Spaghetti & Summits") and identifies the recipient audience. That clearly separates it from the read-only list_* siblings, since this is the only outbound write tool in the set.

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?

It gives an explicit trigger: use when site information is insufficient and contacting owners would be useful, which implies the negative case as well. It does not name alternatives or state outright when not to use it, so it falls short of the top tier.

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.

Resources