IMPOSSIBREW

Skip next delivery

skip_next_delivery

Skips the next delivery of the customer's IMPOSSIBREW subscription. This tool makes no other change. The AI Brewer shows the exact change and makes it only after the customer replies yes. The message goes to the AI Brewer, the same assistant as on impossibrew.co.uk, which checks identity (email plus delivery postcode, or an order number starting EC plus either). message is the customer's own words. The first call has no conversationId; each result returns the conversationId that continues the same conversation across these order tools. The reply is the AI Brewer's complete answer.

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

Input Schema

Name	Required	Description	Default
`message`	Yes
`conversationId`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations only mark it as a non-read-only, non-destructive, non-idempotent open-world write; the description adds real substance on top: a confirmation gate where the change is shown and applied only after the customer replies yes, plus identity verification via email plus postcode or an EC order number. It does not address what happens if skip is requested twice (relevant given idempotentHint=false) or any failure conditions.

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 action and its scope, then flows into confirmation, identity, and conversation threading in a logical order. A few clauses are expandable ('the same assistant as on impossibrew.co.uk'), but each sentence contributes information rather than restating the name.

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?

With no output schema, the description still tells the agent what comes back (the AI Brewer's complete answer plus a conversationId) and what preconditions must hold (identity check, customer confirmation). For a conversational mutation tool with two parameters, that is close to sufficient; only error and repeat-invocation behavior are left uncovered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full load, and it does: message is defined as the customer's own words (not a command syntax), and conversationId is explained as absent on the first call and returned each time to continue the same thread across the order tools. Those are exactly the semantics an agent cannot infer from a bare string field with a regex pattern.

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?

States a specific verb and resource ('Skips the next delivery of the customer's IMPOSSIBREW subscription') and immediately bounds scope with 'This tool makes no other change', which separates it from cancel_subscription and pause_subscription in spirit. It never names those siblings explicitly, so differentiation is implied rather than stated.

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

Usage Guidelines3/5

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

Usage is implied by the verb-plus-resource phrasing and the confirmation ritual (the customer must reply yes before the change lands), which tells the agent this is a conversational, confirmed action. However, it gives no explicit routing guidance against pause_subscription, cancel_subscription, or change_delivery_address, which are the obvious alternatives an agent must choose between.

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

All IMPOSSIBREW 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?