IMPOSSIBREW

Check my order

check_order

Read-onlyIdempotent

Read-only. Looks up the customer's own IMPOSSIBREW orders and subscription: order status, tracking, delivery dates, subscription details, next delivery and store credit. This tool cannot change, cancel or refund anything. 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": "check_order"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations, the description explains identity checks, the AI Brewer handoff, and that the reply is the assistant's complete answer. It also discloses the conversation-state behavior around conversationId, which is important operational context not captured by the readOnly/openWorld/idempotent hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with 'Read-only' and the core capability, then proceeds through limitations, identity, and conversation mechanics in a logical order. Every sentence contributes operational meaning, and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a conversational, identity-verified order lookup with no output schema, the description covers what is returned conceptually (status, tracking, delivery dates, subscription details, store credit, complete answer) and how state is continued via conversationId. It gives an agent enough context to invoke the tool correctly.

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 parameter meaning, and it does: message is the customer's own words, and conversationId is absent on the first call and returned by results to continue the same conversation across order tools. This adds clear semantics beyond the bare schema types and 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?

The description states a specific verb and resource: it looks up the customer's own IMPOSSIBREW orders and subscription, including status, tracking, delivery dates, subscription details, next delivery, and store credit. It also clearly distinguishes this read-only lookup from mutation siblings by saying it cannot change, cancel, or refund anything.

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 gives clear usage context: this is for the customer's own order/subscription questions, is read-only, and requires identity verification. It implies that cancellation, changes, and refunds belong to other tools, but it does not explicitly name the best alternative sibling for every adjacent request.

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?