IMPOSSIBREW

Resume subscription

resume_subscription

Resumes a paused IMPOSSIBREW subscription or restarts a cancelled one. 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": "resume_subscription"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations, which only say readOnly=false and destructive=false. It discloses the human-in-the-loop gate (the AI Brewer shows the exact change and only applies it after the customer replies yes) and the identity check (email plus delivery postcode, or an EC-prefixed order number), which an agent must know before composing a call.

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 what the tool does, then the safety and threading details. Some sentences are telegraphic ("message is the customer's own words."), but nothing is redundant.

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 mutation tool with no output schema and two undocumented parameters, it covers the preconditions, confirmation flow, identity verification, and conversation continuity. It stops short of describing failure modes, such as what the reply looks like when identity verification fails.

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 0%, so the description must carry the parameters, and it does: message is defined as the customer's own words and conversationId is explained as absent on the first call and returned in each result to continue the thread. It does not explain how the specific subscription is identified within the message, which leaves a real gap given that neither parameter is a subscription ID.

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 (resume a paused / restart a cancelled IMPOSSIBREW subscription) and scopes it with "This tool makes no other change," which separates it from pause_subscription and cancel_subscription in the sibling list.

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?

The description makes clear this is the path for pausing's inverse and that it triggers a confirmation dialogue before any change, so an agent knows when it applies. It never explicitly names pause_subscription or cancel_subscription as the alternatives for the opposite action, so routing is clear by implication rather than stated.

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?