Amber's Slime Studio

Search slimes

search_catalog

Read-onlyIdempotent

Search Amber's Slime Studio's handmade slimes by words (name, scent, colour, charms), texture and maximum price. Returns pots with price in GBP, stock, texture, scent, image and product URL, best matches first. Call with no arguments to list everything on sale.

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": "search_catalog"
  }
}

Input Schema

Name	Required	Description
`limit`	No	How many results to return, 1 to 20 (default 10)
`query`	No	Words to match against names, scents, textures, colours and charms, e.g. 'unicorn', 'cherry', 'pink butter'. Omit to browse everything.
`texture`	No	Texture slug or name from list_textures, e.g. 'butter-slime', 'cloud', 'icee', 'thick-and-glossy-slime'
`in_stock_only`	No	When true (default) only slimes that can be ordered now: in stock, or open for pre-order
`max_price_gbp`	No	Highest price per pot in pounds, e.g. 9.5

Output Schema

Name	Required	Description
`items`	Yes	Best matches first
`total`	Yes	Matches before the limit was applied
`shop_note`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Adds meaningful behavior beyond annotations: best matches first, prices in GBP, and included stock, scent, image, and product URL. Annotations already cover read-only, idempotent, non-destructive behavior, so the remaining disclosure is good but lacks pagination or edge-case details.

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?

Two tightly written sentences with the search scope and return fields front-loaded. There is no redundant or wasted wording.

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?

The definition is complete for a search tool: it covers filtering dimensions, no-argument browsing, result ordering, and key return fields. With annotations and a full schema present, only explicit sibling guidance is notably absent.

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 every parameter thoroughly. The description reinforces word, texture, and max-price filtering but adds little syntax or constraint detail beyond the schema.

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?

States a specific verb and resource: searching handmade slimes by words, texture, and maximum price. It clearly describes the search scope and returned fields, but does not explicitly differentiate itself from siblings like get_product or list_textures.

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?

It gives one useful usage cue: call with no arguments to list everything on sale. It does not explain when to prefer this over get_product or list_textures, so usage is implied rather than fully guided.

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?