Skip to main content
Glama

Search sneakers

stockroom_search
Read-only

Search sneaker collection and wishlist by brand, silhouette, colorway, SKU, or tag; set a maximum market price to find affordable wishlist pairs.

Instructions

Search the collection and wishlist by brand, silhouette, colourway, SKU or tag. Use maxMarketPrice to find wishlist pairs that are currently affordable.

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_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoe.g. "kobe", "curry 6", "DQ7"
statusNoall
maxMarketPriceNoOnly pairs whose market price is at most this (USD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful scope fact that it spans both collection and wishlist, and that maxMarketPrice compares against a live market price. It says nothing about result ordering, pagination behavior for limit, or what a pair record contains.

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 sentences, zero filler. Scope and searchable facets come first, then the one non-obvious usage pattern. Nothing is repeated from the title or the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter search tool with no output schema, the definition covers intent and facets but leaves the shape of results, ordering, and how matching works (exact SKU vs. fuzzy text) unstated. Adequate to invoke correctly for simple lookups, thin for predicting what comes back.

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?

With only 50% schema coverage, the description compensates meaningfully: it enumerates the queryable facets (brand, silhouette, colourway, SKU, tag), which the schema reduces to example strings like "kobe" and "DQ7", and it clarifies that maxMarketPrice is about affordability on wishlist pairs. The limit and status parameters get no narrative treatment, though status's enum is self-explanatory.

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 (search) and resources (collection and wishlist), plus the facets searched: brand, silhouette, colourway, SKU, tag. That is far more informative than the title 'Search sneakers' alone. It does not name a sibling to distinguish from, but the sibling set (add, mark bought, overview) is functionally distant enough that ambiguity is low.

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?

The second sentence gives one concrete use case: combine the search with maxMarketPrice to surface affordable wishlist pairs. That is genuinely useful routing guidance for a task intent. However, there is no when-not guidance, no mention of how this differs from stockroom_overview, and no hint about how status=all vs. owned vs. wishlist should be chosen in practice.

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