Skip to main content
Glama

Valentine's Day Gifts – hand-picked gift ideas

Curated gift catalog

get_catalog
Read-only

Paginated curated Valentine gift starters. On amazon.se and amazon.com items include /dp/ASIN buy links (separate curated catalogs per store); on other marketplaces catalogMode is search-ideas. Pass marketplace=amazon.com for the US catalog (English titles, amazon.com/dp/ASIN links) or amazon.se (default); without it, country, then Accept-Language en-US → amazon.com. 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-US, en, sv. amazon.com always answers in English.
offsetNo
countryNoISO country of the shopper, e.g. US or SE. Used when marketplace is omitted (US → amazon.com).
interestNo
occasionNo
categoriesNoComma-separated categories
marketplaceNoAmazon storefront for the end user: amazon.com (United States) or amazon.se (Sweden, default); ids like us/se also work. Pass marketplace=amazon.com for US shoppers to get amazon.com/dp/ASIN links with English titles. If omitted, country is used, then Accept-Language (en-US → amazon.com), else amazon.se. A missing store never errors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "ISO country of the shopper, e.g. US or SE. Used when marketplace is omitted (US → amazon.com).",
      +  "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, en, sv. amazon.com always answers in English."
    • removedInput schema / properties / locale / minLength
      Removed value: -2
    • 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 produce /dp links on amazon.se and amazon.com (US); other marketplaces get romantic search deep-links."New value: +"Amazon storefront for the end user: amazon.com (United States) or amazon.se (Sweden, default); ids like us/se also work. Pass marketplace=amazon.com for US shoppers to get amazon.com/dp/ASIN links with English titles. If omitted, country is used, then Accept-Language (en-US → amazon.com), else amazon.se. A missing store never errors."
    • removedInput schema / properties / marketplace / minLength
      Removed value: -2
    • removedInput schema / required
      Removed value: -[
      -  "marketplace",
      -  "locale"
      -]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses useful behavior: pagination, /dp/ASIN buy links on amazon.se and amazon.com, catalogMode search-ideas on other marketplaces, and the fallback logic for missing marketplace/country/locale. It does not cover rate limits, auth, or exact response fields, so it is strong but not exhaustive.

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?

The description is front-loaded with purpose and then moves into marketplace behavior and fallback rules, which is appropriate. Some marketplace details are repeated between sentences, and the trailing 'OpenAPI: getCatalog' is low-value, but overall it is dense and mostly efficient.

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 10-parameter read-only catalog tool with no output schema, the description covers purpose, marketplace behavior, link formats, fallback rules, and the relationship to search_gifts. It does not describe the returned item fields or pagination metadata, but the essential calling context is present.

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?

The description adds meaningful semantics for marketplace, country, and locale fallback behavior, but it does not explain q, ids, limit, offset, interest, occasion, or categories beyond what the schema already says. With 60% schema description coverage, the schema carries much of the burden, making this adequate but with clear gaps.

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 clearly identifies the resource as paginated curated Valentine gift starters and notes that search_gifts remains primary discovery, which helps distinguish it from the sibling search tool. It is not a direct verb statement, and a few phrases like catalogMode are left unexplained, so it falls short of a fully crisp 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?

It mentions that search_gifts remains primary discovery, implying this tool is for curated browsing, but it does not explicitly say when to use get_catalog versus search_gifts or what the intended use cases are. Marketplace selection guidance is detailed, but it is about parameters rather than tool selection.

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