teas.co.uk

Change a subscription

change_subscription

DestructiveIdempotent

Use this only when a signed in customer clearly asks to pause, resume or cancel one of their teas.co.uk tea subscriptions; confirm which one and which change with them first. subscription_id is the id from my_subscriptions; ids from other accounts are never found. pause needs an active subscription, resume a paused one, and cancel works on either. Cancel is final: a cancelled subscription cannot be resumed here. An unknown id, or a change that does not fit the current status, returns an error and changes nothing. It returns the subscription as it is afterwards. To see the subscriptions first use my_subscriptions.

Input Schema

Name	Required	Description
`action`	Yes	pause stops deliveries until resumed; resume restarts a paused subscription; cancel ends it, and a cancelled subscription cannot be resumed here.
`idempotency_key`	No	Optional. A unique key for this change (8 to 128 letters, digits or . _ : -). Sending the same key again within 24 hours returns the first answer instead of making the change twice.
`subscription_id`	Yes	The id from my_subscriptions.

Output Schema

Name	Required	Description	Default
`done`	Yes
`subscription`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

addedInput schema / properties / idempotency_key

Added value: +{
+  "description": "Optional. A unique key for this change (8 to 128 letters, digits or . _ : -). Sending the same key again within 24 hours returns the first answer instead of making the change twice.",
+  "maxLength": 128,
+  "minLength": 8,
+  "pattern": "^[A-Za-z0-9._:-]{8,128}$",
+  "type": "string"
+}

Changed1 schema field changedOct 5, 2026

addedInput schema / properties / action / description

Added value: +"pause stops deliveries until resumed; resume restarts a paused subscription; cancel ends it, and a cancelled subscription cannot be resumed here."

First observedOct 5, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations cover safety (destructiveHint, idempotentHint), but the description adds state-dependent preconditions (pause needs active, resume needs paused, cancel works on either), irreversibility ('a cancelled subscription cannot be resumed here'), error semantics ('returns an error and changes nothing'), and the post-state return. That is substantial context beyond the structured fields.

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-loads the when-to-use constraint and then the behavioral rules; every sentence carries a constraint or state rule. It is dense but not padded, though it runs long and could be slightly tightened.

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?

An output schema exists, so return values need not be detailed, and the description still notes the post-state ('returns the subscription as it is afterwards'). Preconditions, error behavior, and sibling routing are all present for a destructive mutation tool.

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 100%, so the schema already documents action and subscription_id, but the description adds meaning: subscription_id must come from my_subscriptions and ids from other accounts are 'never found', plus the status precondition for each action value. This goes beyond the schema's enum gloss.

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/resume/cancel a teas.co.uk tea subscription) and explicitly scopes it against siblings by naming my_subscriptions for viewing. An agent can distinguish it from start_subscription or my_subscriptions 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 Guidelines5/5

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

Gives explicit when-to-use ('only when a signed in customer clearly asks'), a required precondition ('confirm which one and which change with them first'), and names the alternative tool to call first ('To see the subscriptions first use my_subscriptions'). Routing and exclusions are fully covered.

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

All teas.co.uk 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?