Skip to main content
Glama

Mother's Day Gifts – hand-picked gift ideas

Curated Mother's Day catalog

get_catalog
Read-only

Paginated curated Mother's Day gift starters. On amazon.se (SE catalog) and amazon.com (US catalog) items include /dp/ASIN links; on other marketplaces catalogMode is search-ideas. Pass marketplace + locale (marketplace=amazon.com for US/English, amazon.se for Sweden; if omitted, Accept-Language en-US → amazon.com, else amazon.se). Search (search_gifts) remains primary discovery. OpenAPI: getCatalog.

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

Input Schema

NameRequiredDescriptionDefault
qNoFull-text filter
idsNoComma-separated catalog ids
limitNo
localeNoUser locale, e.g. en, sv, de, fr, es (mothers day / mors dag / Muttertag / fête des mères / día de la madre)
offsetNo
interestNo
occasionNo
styleTagNo
budgetBandNo
marketplaceNoAmazon storefront for the end user, e.g. amazon.se, amazon.com, us, se, de. Recommended: pass marketplace=amazon.com for US shoppers (US catalog, English, USD, tag sw-mothersday-20) and amazon.se for Sweden (SE catalog, tag sw-mothersday-21). If omitted: Accept-Language en-US → amazon.com, otherwise amazon.se. Other storefronts get Mother's Day search links.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / marketplace / description
      Previous value: -"Amazon storefront domain or id for the end user, e.g. amazon.se, amazon.com, se, de. REQUIRED — curated ASINs only produce /dp links on amazon.se; other marketplaces get Mother's Day search deep-links."New value: +"Amazon storefront for the end user, e.g. amazon.se, amazon.com, us, se, de. Recommended: pass marketplace=amazon.com for US shoppers (US catalog, English, USD, tag sw-mothersday-20) and amazon.se for Sweden (SE catalog, tag sw-mothersday-21). If omitted: Accept-Language en-US → amazon.com, otherwise amazon.se. Other storefronts get Mother's Day search links."
    • removedInput schema / required
      Removed value: -[
      -  "marketplace",
      -  "locale"
      -]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real behavioral detail beyond them: items carry /dp/ASIN links only on amazon.se and amazon.com, while other marketplaces fall back to catalogMode=search-ideas. It also discloses the omission-default resolution (Accept-Language en-US → amazon.com, else amazon.se), which meaningfully affects output shape. It doesn't mention pagination totals or rate limits, so not quite a 5.

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?

Front-loads the resource and the search_gifts alternative, then packs marketplace routing into a compact parenthetical. Dense but every sentence carries information; the clause-embedded defaults are slightly hard to parse but nothing is wasted.

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?

A read-only, 10-parameter, no-output-schema list tool. The description covers the marketplace-dependent return differences and locale defaults, which are the highest-risk ambiguities, and annotations cover the safety profile. The main remaining gap is that most filter parameters (styleTag, budgetBand, occasion) are left entirely to the enum values.

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 only 40% across 10 parameters, and the description compensates thoroughly for marketplace and locale (including fallback behavior) and implies limit/offset via 'paginated'. However, q, ids, interest, occasion, styleTag, and budgetBand get no explanation in the description beyond their enum values, leaving a real gap for a low-coverage schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific resource and shape ('Paginated curated Mother's Day gift starters'), so an agent immediately knows this returns a browsable catalog rather than a search result. It explicitly positions itself against the sibling search_gifts by calling that the 'primary discovery' path, making the distinction clear without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States that 'Search (search_gifts) remains primary discovery,' which is an explicit usage steer toward the alternative and implies this tool is for browsing curated starters rather than targeted queries. It also gives concrete marketplace/locale routing rules, but stops short of an explicit when-not-to-use or a full decision matrix.

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