Amber's Slime Studio

Create basket link

create_basket_link

Read-onlyIdempotent

Build a link to slime-studio.co.uk that opens the shopper's basket pre-filled with these slimes (and an optional promo code), with the subtotal and estimated standard delivery. Give the link to the shopper: they review the basket and pay on Stripe Checkout. Creates no order and needs no personal data. UK delivery only.

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": {
      "items": "<items>"
    },
    "name": "create_basket_link"
  }
}

Input Schema

Name	Required	Description
`items`	Yes	The slimes to put in the basket, 1 to 20 lines; repeated slugs are combined
`source`	No	Optional short tag for your app or agent, lowercase letters, digits, '.', '_' or '-' (e.g. 'claude'). Defaults to 'mcp'.
`promo_code`	No	Optional promo code to pre-fill; checkout validates it

Output Schema

Name	Required	Description
`note`	Yes
`items`	Yes
`notes`	Yes	Adjustments made to the request, if any
`basket_url`	Yes	Give this link to the shopper; it opens their basket on slime-studio.co.uk
`item_count`	Yes
`promo_code`	Yes
`subtotal_gbp`	Yes	Slimes subtotal in pounds sterling (GBP), e.g. 8.99
`subtotal_pence`	Yes	Slimes subtotal in pence (GBP minor units), e.g. 899
`estimated_standard_shipping_gbp`	Yes	Standard UK delivery for this basket in pounds sterling (GBP), e.g. 8.99
`estimated_standard_shipping_pence`	Yes	Standard UK delivery for this basket in pence (GBP minor units), e.g. 899

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description reinforces this with two genuinely additive facts: no order is created, no personal data is needed, and sales are UK-only. It still says nothing about link lifetime/expiry or what happens if a slug is unknown, which matters for a generated link.

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 core action, followed by the downstream workflow, the non-effects, and the geographic constraint. No sentence is 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?

An output schema exists, so return-value explanation is unnecessary, and annotations carry the safety profile. Given that, the description covers purpose, handoff, side-effect absence, data requirements, and delivery scope — everything needed to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 items, slug, qty caps, and promo_code. The description only mirrors that ('pre-filled with these slimes (and an optional promo code)') and adds nothing about the source tag or line-combining behavior, so baseline 3 applies.

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 artifact (build a basket link to slime-studio.co.uk) plus what the link contains: pre-filled slimes, optional promo code, subtotal and estimated standard delivery. The 'creates no order' clause separates it from any checkout/order tool in the sibling set.

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?

Explicitly frames the handoff: give the link to the shopper, who reviews and pays on Stripe Checkout. Also states a hard scoping constraint (UK delivery only). It does not name alternatives such as check_promo or get_shipping_options, so it stops short of full when/when-not routing.

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

All Amber's Slime Studio 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?