teas.co.uk

Reward points

rewards_balance

Read-onlyIdempotent

Use this when a signed in customer asks how many teas.co.uk reward points they have or what they are worth. It takes no input. Zero points is a normal answer for a new account. Without a linked account it returns an error asking the customer to sign in. Points are only spent at checkout on teas.co.uk, so this cannot redeem them. To buy, use checkout_link; for past orders use my_orders.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`url`	No
`tier`	No
`points`	Yes
`unlocks`	No	What the points unlock, cheapest first. Redeemed on teas.co.uk only.
`how_to_use`	No
`worth_text`	No
`spent_lifetime`	No
`earned_lifetime`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

addedOutput schema / properties / unlocks

Added value: +{
+  "description": "What the points unlock, cheapest first. Redeemed on teas.co.uk only.",
+  "items": {
+    "properties": {
+      "affordable": {
+        "description": "True when the balance covers it.",
+        "type": "boolean"
+      },
+      "kind": {
+        "description": "voucher, charity, physical or flex.",
+        "type": "string"
+      },
+      "label": {
+        "type": "string"
+      },
+      "points": {
+        "description": "Points it costs.",
+        "type": "integer"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

First observedOct 5, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, and the description adds genuinely new behavioral facts: no input is required, zero points is a valid answer, a missing linked account produces a sign-in error, and points cannot be redeemed here. That is real 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.

Conciseness5/5

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

Four short sentences, front-loaded with the trigger condition, then edge cases, then sibling routing. Every sentence carries distinct information with no padding or repetition of the title.

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 formatting need not be described; the description still covers the non-error zero case and the error path. Combined with sibling routing and the redemption limitation, nothing an agent needs to call this correctly is missing.

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?

The tool takes zero parameters, so the baseline is 4; the description correctly confirms 'It takes no input,' which matches the empty schema and additionalProperties=false. There are no parameter semantics to expand further.

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 ('asked how many teas.co.uk reward points they have or what they are worth') and scopes it to signed-in customers. An agent can distinguish this from sibling tools like get_profile or checkout_link without opening the 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?

Explicitly names when to use it, notes the sign-in precondition, and routes the agent to alternatives: checkout_link for buying and my_orders for past orders. It also states a negative capability ('this cannot redeem them'), which prevents a likely misuse.

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?