Skip to main content
Glama

Dorm Kit – hand-picked gift ideas

Create and fill dorm kit

create_and_fill_kit

One-shot: create a dorm kit and fill from itemQueries, itemKeywords, and/or itemAsins. marketplace=amazon.com + locale=en-US for US shoppers; amazon.se for Sweden. Missing store falls back (en-US → amazon.com, else amazon.se).

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

Input Schema

NameRequiredDescriptionDefault
localeNoBCP-47 locale for the shopper (e.g. en-US, sv-SE). Recommended; en-US without a marketplace selects amazon.com.
roomTypeNo
dormRulesNo
itemAsinsNo
budgetBandNo
universityNo
itemQueriesNo
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).
studentNameNo
itemKeywordsNo

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
    • removedInput schema / required
      Removed value: -[
      -  "marketplace",
      -  "locale"
      -]
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the marketplace fallback chain (en-US → amazon.com, else amazon.se) and that a missing store is not an error, which is real value. It says nothing about side effects, whether an existing kit is reused or duplicated, or what the response contains for what is clearly a write operation.

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?

Three compact sentences with the core action front-loaded and no filler. The telegraphic phrasing ("Missing store falls back") is dense but briefly cryptic, costing a little clarity for its brevity.

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?

A 10-parameter mutation tool with no annotations and no output schema needs more than this. The description covers input sourcing and store resolution, but omits return shape, whether the created kit is persisted and under what identity, and any guidance on the five undocumented structural parameters.

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 20% across 10 parameters, so the description must compensate. It does well on the two genuinely ambiguous parameters, marketplace and locale, explaining accepted forms and the fallback resolution, and it names the three item-input parameters. The remaining five (roomType, dormRules, budgetBand, university, studentName) are left entirely to their self-explanatory names with no semantic detail.

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 ("create a dorm kit and fill") and names the three input vectors that drive the fill step. It implies the one-shot nature relative to create_kit plus add_kit_item but never names those siblings explicitly, so differentiation is by inference rather than statement.

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?

"One-shot" signals this is the single-call alternative to the create-then-add flow, but the description never states when to prefer it over create_kit or add_kit_item, nor any prerequisites. The marketplace/locale guidance is conditional setup advice for calling this tool, not tool-selection guidance.

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