Skip to main content
Glama

Add a sneaker

stockroom_add_pair

Add a pair to a wishlist or owned collection using its SKU; the server fills canonical details and blocks duplicate entries.

Instructions

Add a pair to the wishlist (default) or the collection. With a SKU / style code, the server fills in the canonical name, colourway, photo and market price from KicksDB. Duplicates are detected and not added twice. Needs the owner token.

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

Input Schema

NameRequiredDescriptionDefault
skuNoStyle code, e.g. "CW2190-300"
sizeNo
brandNo
modelNoSilhouette, e.g. "Kobe 6 Protro"
notesNo
priceNoTarget price (wishlist) or price paid (owned)
statusNowant
colorwayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses real behavior: server-side enrichment of name/colourway/photo/market price from KicksDB when a SKU is supplied, duplicate suppression, and an owner-token requirement. It does not describe failure behavior (e.g. what happens if the SKU lookup misses or the token is absent), so it is strong but not exhaustive. The KicksDB fetch is a server-side enrichment step, so it does not meaningfully contradict openWorldHint=false.

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 purpose and destination, then enrichment, dedupe, and the auth requirement. Every sentence carries distinct information and nothing is repeated from the schema.

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 an 8-parameter write tool with no output schema, the description covers the crucial mechanics: destination default, enrichment path, idempotency, and auth. It falls short on per-field expectations (size format, notes/brand purpose) and on what a successful call returns, but the core is covered.

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 description coverage is only 38%, and the description compensates for the most important case: giving a SKU means name, colourway, photo and price are filled automatically, which implies those fields are optional. It also disambiguates price as target price vs price paid, but leaves size, brand, notes, status and model without added meaning 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?

The description states a specific verb and resource ('Add a pair') and scopes the destination ('wishlist (default) or the collection'), which is concrete enough to act on. It does not name a sibling such as stockroom_mark_bought to explicitly separate moving an item into the collection from creating a new entry, so it stops short of full sibling differentiation.

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?

It clarifies the default destination (wishlist) versus the collection and notes that duplicates are silently skipped, which tells the agent what will happen on repeat calls. It gives no explicit when-not guidance or named alternative for promoting an existing pair, which keeps it below a 5.

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