Amber's Slime Studio

Get slime details

get_product

Read-onlyIdempotent

Full details for one slime by slug or sku: description, features, ingredients, care instructions, FAQs, video, restock date, age guidance (3+), dispatch and returns policy.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_product"
  }
}

Input Schema

Name	Required	Description	Default
`sku`	No	Product sku from search_catalog. Give slug or sku.
`slug`	No	Product slug from search_catalog, e.g. 'cotton-candy-swirl'

Output Schema

Name	Required	Description
`sku`	Yes	Stable product code
`tag`	Yes	Shop label such as 'Bestseller' or 'New'
`url`	Yes	Product page on slime-studio.co.uk
`faqs`	Yes
`name`	Yes
`size`	Yes
`slug`	Yes	Product slug; use it with get_product, check_promo and create_basket_link
`scent`	Yes
`weight`	Yes
`age_min`	Yes	Minimum age in years
`texture`	Yes
`age_note`	Yes
`features`	Yes
`in_stock`	Yes
`image_url`	Yes
`price_gbp`	Yes	Price per 250ml pot in pounds sterling (GBP), e.g. 8.99
`video_url`	Yes
`about_text`	Yes
`updated_at`	Yes
`ingredients`	Yes
`price_pence`	Yes	Price per pot in pence (GBP minor units), e.g. 899
`returns_url`	Yes
`safety_note`	Yes
`restock_date`	Yes	Expected restock date (ISO) when sold out, else null
`texture_slug`	Yes	Texture slug, as used by list_textures and the texture filter
`dispatch_note`	Yes
`returns_summary`	Yes
`preorder_allowed`	Yes	True if it can be ordered while out of stock
`care_instructions`	Yes
`short_description`	Yes
`original_price_gbp`	Yes	Pre-sale price in GBP when the slime is on sale, else null
`detailed_description`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description contributes by enumerating what content is surfaced (care instructions, FAQs, restock date, dispatch and returns policy) and a policy note like age guidance (3+), but says nothing about error behavior for an unknown slug/sku or whether both keys may be supplied together.

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?

A single front-loaded sentence with the resource and lookup keys first, followed by the content inventory. The field enumeration is somewhat long and partially redundant with the output schema, but every item listed still informs scope.

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 two-parameter read tool with full annotations and an output schema, this is close to complete: it names the resource, the identifiers, and the content categories. The only real gap is guidance on choosing between slug and sku when both are present.

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% and the schema already explains that slug or sku come from search_catalog. The description merely repeats 'by slug or sku' without clarifying precedence if both are passed or that zero required parameters means one of the two is expected.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource (one slime, full details) and the two lookup keys (slug or sku), matching the tool name 'get_product'. It is clear what it does, but it never names a sibling such as search_catalog, so an agent must infer the distinction from the wording alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied rather than stated: it looks up one item by identifier, which suggests it should follow a catalog search. There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named.

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?