Skip to main content
Glama

Dorm Kit – hand-picked gift ideas

Search dorm kit items

search_kit_items

Search dorm / back-to-school essentials. Returns Amazon search deep-links (and optional catalog matches). Pass marketplace=amazon.com + locale=en-US for US shoppers (amazon.com links, English queries) or marketplace=amazon.se for Sweden. Missing store falls back (en-US → amazon.com, else amazon.se).

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": {
      "q": "<q>"
    },
    "name": "search_kit_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query, e.g. desk lamp or twin XL sheets
limitNoMax results (1-20)
localeNoBCP-47 locale for the shopper (e.g. en-US, sv-SE). Recommended; en-US without a marketplace selects amazon.com.
roomTypeNoRoom type filter
dormRulesNoResidence constraints, e.g. no-candles, no-hot-plates
budgetBandNoBudget band
universityNoOptional university / campus context
marketplaceNoAmazon storefront id (us, se) or domain (amazon.com, amazon.se). Recommended. For US shoppers pass marketplace=amazon.com (US catalog, amazon.com /dp/ links, tag sw-dormkit-20). If omitted: locale en-US selects amazon.com, anything else falls back to amazon.se (never an error).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / locale / description
      Previous value: -"BCP-47 locale for the shopper (e.g. en-US, sv-SE). REQUIRED."New value: +"BCP-47 locale for the shopper (e.g. en-US, sv-SE). Recommended; en-US without a marketplace selects amazon.com."
    • removedInput schema / properties / locale / minLength
      Removed value: -1
    • changedInput schema / properties / marketplace / description
      Previous value: -"Amazon marketplace id (e.g. us, se) or domain (e.g. amazon.com, amazon.se). REQUIRED."New value: +"Amazon storefront id (us, se) or domain (amazon.com, amazon.se). Recommended. For US shoppers pass marketplace=amazon.com (US catalog, amazon.com /dp/ links, tag sw-dormkit-20). If omitted: locale en-US selects amazon.com, anything else falls back to amazon.se (never an error)."
    • removedInput schema / properties / marketplace / minLength
      Removed value: -1
    • changedInput schema / required
      Previous value: -[
      -  "q",
      -  "marketplace",
      -  "locale"
      -]New value: +[
      +  "q"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the meaningful behavior: results are deep-links (not product records), catalog matches are optional, and a missing store never errors but falls back deterministically. It omits rate limits, auth needs, and dedup/pagination behavior for links, keeping it out of 5 territory.

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?

Four sentences, front-loaded with purpose before the marketplace mechanics, with no filler sentences. The fallback rule is stated twice in slightly different words ('Missing store falls back' vs the parenthetical), which is minor waste but keeps it from a 5.

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 search tool with no output schema and no annotations, the description covers the two things structured fields cannot: the return shape (deep-links) and the storefront resolution rule. The filter parameters are fully documented in the schema, so their absence here is acceptable; only cross-tool routing guidance is genuinely missing.

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 100%, so the baseline is 3. The description restates the marketplace/locale pairing already in the schema but adds that en-US yields English queries against amazon.com, a small amount of meaning beyond the field docs. The other six parameters (roomType, dormRules, budgetBand, university, limit) are untouched by the description.

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 opening sentence pairs a specific verb ('Search') with a specific domain ('dorm / back-to-school essentials') and immediately states what comes back: Amazon search deep-links plus optional catalog matches. It never names a sibling (e.g. list_catalog_items or resolve_product) to say how it differs, so it falls short of a 5.

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 marketplace/locale guidance implies the tool is for shopper-facing product discovery and tells the agent how to pick a storefront, but there is no explicit statement of when to prefer this over resolve_product or list_catalog_items. Usage is only inferable from context, and no exclusions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources