Dorm Kit – hand-picked gift ideas

List curated dorm catalog

list_catalog_items

Browse the hand-picked dorm essentials catalog for a storefront. marketplace=amazon.com (US) returns verified amazon.com /dp/ product links; marketplace=amazon.se returns the Swedish catalog with amazon.se /dp/ links. Optional q/category filters.

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

Input Schema

Name	Required	Description
`q`	No	Optional text filter, e.g. twin xl, lamp
`limit`	No	Max items returned (default 25)
`category`	No	Optional category filter
`marketplace`	No	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).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description must carry the full load. It does disclose useful behavior specific to each marketplace, including the /dp/ link format and which catalog each storefront returns, but it says nothing about read-only versus mutating semantics, default/maximum result counts, or ordering of results.

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 short sentences, front-loaded with the resource and then the marketplace semantics. Little waste, although the marketplace sentence duplicates information already in the schema.

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 a no-required-parameter listing tool with full schema coverage and no output schema, the description covers scope, storefront behavior, and result-link form. It doesn't describe what fields each catalog item contains, a minor gap for an agent deciding whether to call it.

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 q, limit, category, and marketplace are already fully documented. The description restates the q/category filters and marketplace-to-catalog mapping but adds no new syntax or format details, so the baseline of 3 applies.

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 has a clear verb ('Browse') and a specific resource ('hand-picked dorm essentials catalog for a storefront'), and it explains the two marketplace variants with their link formats. It never names a sibling such as search_kit_items or resolve_product to route the agent explicitly, which keeps it from 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?

Usage is only implied: the mention of 'Optional q/category filters' hints at how to narrow the result set, and 'for a storefront' suggests a browsing scenario. There is no explicit statement of when to choose this over search_kit_items or list_marketplaces and no exclusions.

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

All Dorm Kit – hand-picked gift ideas tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?