IMPOSSIBREW

Pause subscription

pause_subscription

Pauses the customer's IMPOSSIBREW subscription for 1, 2 or 3 months. 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": "pause_subscription"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent, open-world mutation. Beyond that the description adds genuinely useful behavior: no other change is made, confirmation is required before applying, identity verification is enforced upstream, and the call hands off to an external assistant. It does not cover failure modes (identity mismatch, ineligible subscription) or whether an existing scheduled change is affected.

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?

Purpose and duration scope are front-loaded, then the confirmation/identity/conversation mechanics follow in a logical order. The middle sentence is long and clause-chained ("the same assistant as on impossibrew.co.uk, which checks identity..."), but no sentence is expendable.

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 correctly says the reply is the AI Brewer's complete answer and explains how conversationId round-trips. The one real gap is that no parameter carries the chosen duration, and the description never says the agent must express the 1/2/3-month choice inside the message text.

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 description coverage is 0%, so the description carries the full load and does: message is the customer's own words sent to the AI Brewer, and conversationId is absent on the first call and echoed by each result to continue the same conversation. That is meaning the schema's bare string types cannot convey.

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 (pause the customer's IMPOSSIBREW subscription) plus the exact scope (1, 2 or 3 months) and an explicit boundary ("This tool makes no other change"), which separates it from cancel_subscription, resume_subscription and skip_next_delivery without naming them.

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?

Gives a concrete interaction protocol: the AI Brewer previews the exact change and acts only after the customer says yes, and identity must be verified via email plus postcode or an EC order number. It does not explicitly name the sibling to use for the inverse action (resume_subscription) or state when a pause is inappropriate, so it stops short of full alternative routing.

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?