IMPOSSIBREW

Change delivery address

change_delivery_address

Destructive

Changes the UK delivery address of one IMPOSSIBREW order that has not left the warehouse. 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": "change_delivery_address"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations flag a destructive, non-idempotent, open-world write, and the description adds material context the annotations cannot express: only the address changes, nothing else is touched, identity is verified via email plus postcode or an EC-prefixed order number, and confirmation is gated on the customer's explicit yes. That is exactly the behavior an agent needs before invoking a destructive mutation.

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?

The opening sentence front-loads what the tool does and the exclusion follows immediately. A few clauses about the AI Brewer and the impossibrew.co.uk assistant are slightly repetitive, but the conversationId mechanics paragraph earns its space.

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 destructive two-parameter tool with no output schema, the description covers preconditions, confirmation flow, identity verification and the return value (the AI Brewer's complete answer). It stops short of saying what an invalid or expired conversationId produces, which is a minor residual gap.

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 must carry both parameters, and it does: message is the customer's own words and conversationId is absent on the first call and returned by each result to continue the same conversation. Both parameters gain meaning beyond the raw type and pattern constraints.

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?

A specific verb (changes) plus a precisely scoped resource (the UK delivery address of one IMPOSSIBREW order that has not left the warehouse). The warehouse constraint alone distinguishes it from cancel_order and report_order_problem, so an agent can route correctly without opening a schema.

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 clear precondition (order must not have left the warehouse) and an explicit operational rule: the change is shown to the customer and made only after they reply yes. It never names the sibling to use when the order has already shipped, which is the one routing gap.

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?