within

One boutique's stock

boutique_shelf

Read-onlyIdempotent

Retrieve live stock for one named boutique, newest first, with sizes and prices; search inside that shop to find specific items by name or category.

Instructions

One boutique's stock right now, newest first, with sizes and prices; a query searches inside that shop only. Use this when someone names a boutique ('what does WDLT117 have', 'show me Utopia's sneakers') or wants to browse one shop. boutique_domain is the domain shown on any boutique or item.

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": {
      "boutique_domain": "<boutique_domain>"
    },
    "name": "boutique_shelf"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Default 12.
`query`	No	Search inside this boutique only.
`offset`	No
`boutique_domain`	Yes	The boutique's domain, as shown on boutiques and pieces (e.g. 'utopia-kicks.myshopify.com').

Output Schema

Name	Required	Description	Default
`pieces`	Yes
`boutique`	Yes
`view_url`	Yes
`next_offset`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Nov 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds behaviour beyond that: results are ordered newest first, each item carries sizes and prices, and any query is constrained to the named shop. Pagination behaviour is left unstated, but that is a modest gap.

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?

Front-loaded with the resource and ordering, then the usage triggers, then the key parameter hint — every clause carries information. The semicolon-heavy single paragraph is dense but not padded.

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?

An output schema exists, so return values need no explanation, and the description covers scope, ordering, and the required identifier's provenance. Only paging semantics (offset) are absent, which is minor for a 4-parameter, single-shop listing tool.

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?

Schema coverage is 75%, so the structured fields already do most of the work. The description still adds value by explaining where boutique_domain comes from ('the domain shown on any boutique or item') and reinforcing that query is scoped locally, though offset remains undocumented in both places.

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+resource ('One boutique's stock right now') with scope ('a query searches inside that shop only') and result shape (newest first, sizes and prices). The 'that shop only' framing clearly separates it from catalogue-wide searches without needing sibling schemas.

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?

Gives concrete when-to-use triggers with realistic phrasings ('what does WDLT117 have', 'show me Utopia's sneakers') and the browse-one-shop case. It does not explicitly name the alternative to use instead for cross-boutique search, so the routing is implied rather than spelled out.

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