Skip to main content
Glama

SOMA Non-Alcoholic Craft Beer

Join the SOMA Founding Fifty waitlist

join_waitlist
Idempotent

Registers an adult user's interest in the Founding Fifty pre-launch programme. Current benefits and availability require confirmation; signup does not confirm a tasting, discount or delivery date. Only call with explicit consent: it stores contact details in SOMA's CRM and sends a one-time welcome email. Idempotent: signing up twice never double-sends.

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>"
    },
    "name": "join_waitlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoThe user's city, so SOMA knows where to launch next (optional)
nameNoThe user's first name (optional)
emailYesThe user's email address (required, with their consent)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag non-read-only, idempotent, open-world and non-destructive behavior. The description adds side effects the annotations cannot convey: contact details go into SOMA's CRM and a one-time welcome email is sent. The idempotency claim is partly redundant with idempotentHint=true, but 'never double-sends' gives it concrete meaning.

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?

Four tight sentences, front-loaded with what the tool does, followed by caveats and the consent rule. Every sentence carries information; the only mild redundancy is restating idempotency already present in annotations, though it does so with added specificity.

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 three-parameter write tool with no output schema, the description covers purpose, consent prerequisite, data destination, email side effect, and expectation-setting about unconfirmed benefits. It does not describe the response or error behavior, but given the simplicity of the operation, an agent has enough to invoke it correctly.

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 email, name and city are already documented in the schema, including that email is required with consent. The description reinforces the consent framing around contact details but adds no field-level detail beyond what the schema says. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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: 'Registers an adult user's interest in the Founding Fifty pre-launch programme.' That is far more precise than the title alone and makes clear this is a signup, not a lookup. It does not explicitly contrast itself with the get_* siblings, but with only one mutation tool in the set, the distinction is easy to infer.

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 prerequisite: 'Only call with explicit consent,' which is a real when-to-use condition an agent could otherwise get wrong. It also sets expectations that signup does not confirm a tasting, discount or delivery date. No alternative tool is named, but no viable alternative exists for this action.

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