Skip to main content
Glama

Dorm Kit – hand-picked gift ideas

Create dorm kit

create_kit

Create an empty or pre-filled dorm kit wishlist. Returns id, editToken, ownerUrl, roommateUrl. 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_kit"
  }
}

Input Schema

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

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.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the return values (id, editToken, ownerUrl, roommateUrl) and that a missing store falls back rather than erroring, but says nothing about write semantics, whether the editToken is a secret, persistence, or failure modes beyond the marketplace fallback.

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 tight sentences, front-loaded with purpose and return values, then the marketplace/locale rule. A little duplication with the schema's marketplace description, but no filler.

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?

It covers the most important non-schema facts—returned tokens/URLs (there is no output schema) and storefront fallback—but for an 8-parameter creation tool with a nested items array and no annotations, the description is too thin on what the other inputs do and how the items list should be shaped.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%, so the description must compensate. It reinforces the marketplace/locale behavior already documented in the schema but leaves the items array structure (asin, url, title, searchKeywords), roomType, dormRules, budgetBand, university, and studentName unexplained.

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 first sentence names a specific verb and resource: create a dorm kit wishlist, and notes it can be empty or pre-filled. It does not, however, explicitly distinguish itself from the sibling create_and_fill_kit, which likely overlaps with the 'pre-filled' path.

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?

It gives parameter-level guidance about choosing amazon.com with en-US for US shoppers and amazon.se for Sweden, plus the fallback rule. It never states when to use this tool versus create_and_fill_kit or add_kit_item, so tool selection is left implied.

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