Skip to main content
Glama

Pet Welcome Box – hand-picked gift ideas

Create pet kit list

create_wishlist

Create an empty pet welcome-kit list. Returns id, editToken, ownerUrl, shopUrl. Pass marketplace (amazon.com for US, amazon.se for Sweden) + locale.

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_wishlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
stageNo
localeNoUser locale, e.g. en-US (US shoppers → amazon.com) or sv-SE (Sweden → amazon.se). If marketplace and country are omitted, en-US selects amazon.com.
countryNoISO country of the shopper, used when marketplace is omitted: US → amazon.com, SE → amazon.se.
petNameNo
speciesNo
sizeBandNo
budgetBandNo
marketplaceNoAmazon storefront: amazon.com (United States — 224 hand-picked products, English, USD, /dp/ links tagged sw-petbox-20) or amazon.se (Sweden, default — 440 products, tag sw-petbox-21); ids us / se also work. Optional: when omitted → country, then locale / Accept-Language en-US → amazon.com, otherwise amazon.se. Other storefronts get search links.
kitCategoriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "ISO country of the shopper, used when marketplace is omitted: US → amazon.com, SE → amazon.se.",
      +  "maxLength": 3,
      +  "minLength": 2,
      +  "type": "string"
      +}
    • changedInput schema / properties / locale / description
      Previous value: -"User locale, e.g. en, sv, de, fr, es"New value: +"User locale, e.g. en-US (US shoppers → amazon.com) or sv-SE (Sweden → amazon.se). If marketplace and country are omitted, en-US selects amazon.com."
    • changedInput schema / properties / marketplace / description
      Previous value: -"Amazon storefront domain or id, e.g. amazon.com, amazon.se, us, se. REQUIRED."New value: +"Amazon storefront: amazon.com (United States — 224 hand-picked products, English, USD, /dp/ links tagged sw-petbox-20) or amazon.se (Sweden, default — 440 products, tag sw-petbox-21); ids us / se also work. Optional: when omitted → country, then locale / Accept-Language en-US → amazon.com, otherwise amazon.se. Other storefronts get search links."
    • 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?

Annotations already declare readOnlyHint=false and openWorldHint=true, so the mutation and open-world nature are covered. The description adds useful return fields (id, editToken, ownerUrl, shopUrl), but does not explain side effects, editToken handling, or marketplace fallback behavior beyond a brief note.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, front-loaded with the core action, and every sentence carries useful information about creation, returns, or marketplace/locale input.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 9 optional parameters, 33% schema coverage, and no output schema, the description is too thin. It names only two parameters and the return fields, but omits how the other pet/kit parameters shape the created list or how defaults are resolved beyond marketplace selection.

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 33% across 9 parameters. The description mentions marketplace and locale, but does not explain the other six parameters such as petName, species, sizeBand, budgetBand, kitCategories, stage, or country, leaving much of the surface undocumented.

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 an empty pet welcome-kit list.' The word 'empty' helps distinguish it from the sibling create_and_fill, though the description does not explicitly name that alternative.

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 a minimal usage instruction to pass marketplace and locale, and the word 'empty' implies use when a blank list is wanted. However, it never explicitly says when to choose this over create_and_fill or add_item, so the guidance is only 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