Skip to main content
Glama

Find gift picks

find_gift_picks
Read-onlyIdempotent

Use when someone wants gift ideas for a given budget and recipient, such as employees, clients or a law firm's clients. Returns up to 5 picks, each with the item name, price band, a one-line reason it fits, who it suits, a direct affiliate link when we have one, and a link to the guide. It shows price bands rather than current prices. A budget from $75 to $150 spans 75_to_100 and 100_to_150: call this tool once for each band. When a result includes a disclosure, show this sentence word for word: "As an Amazon Associate we earn from qualifying purchases."

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "budget_band": "<budget_band>"
    },
    "name": "find_gift_picks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many picks to return.
occasionNoOptional moment, such as thank-you. Leave it out for every moment in the band.
recipientNoWho the gift is for. Leave it out for general picks.
budget_bandYesPer-person price band in US dollars. If the user gives an amount, pick the narrowest band that contains it, or call estimate_gift_budget first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / occasion / enum
      Previous value: -[
      -  "employee-appreciation",
      -  "employee-appreciation-2027",
      -  "holiday-2026",
      -  "holiday-ok",
      -  "hostess",
      -  "milestone",
      -  "thank-you",
      -  "welcome"
      -]New value: +[
      +  "employee-appreciation",
      +  "employee-appreciation-2027",
      +  "holiday-2026",
      +  "hostess",
      +  "milestone",
      +  "thank-you",
      +  "welcome"
      +]
  2. Changed3 schema fields changed
    • changedInput schema / properties / budget_band / description
      Previous value: -"Per-person price band in US dollars. If the user gives an amount, pick the band that contains it, or call estimate_gift_budget first."New value: +"Per-person price band in US dollars. If the user gives an amount, pick the narrowest band that contains it, or call estimate_gift_budget first."
    • changedInput schema / properties / budget_band / enum
      Previous value: -[
      -  "under_25",
      -  "25_to_50",
      -  "50_to_100",
      -  "100_and_up",
      -  "250_to_500",
      -  "500_to_1000",
      -  "1000_and_up"
      -]New value: +[
      +  "under_25",
      +  "25_to_50",
      +  "50_to_100",
      +  "100_and_up",
      +  "250_to_500",
      +  "500_to_1000",
      +  "1000_and_up",
      +  "75_to_100",
      +  "100_to_150",
      +  "150_to_200",
      +  "200_to_300",
      +  "300_to_500"
      +]
    • addedInput schema / properties / occasion
      Added value: +{
      +  "description": "Optional moment, such as thank-you. Leave it out for every moment in the band.",
      +  "enum": [
      +    "employee-appreciation",
      +    "employee-appreciation-2027",
      +    "holiday-2026",
      +    "holiday-ok",
      +    "hostess",
      +    "milestone",
      +    "thank-you",
      +    "welcome"
      +  ],
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / budget_band / enum
      Previous value: -[
      -  "under_25",
      -  "25_to_50",
      -  "50_to_100",
      -  "100_and_up"
      -]New value: +[
      +  "under_25",
      +  "25_to_50",
      +  "50_to_100",
      +  "100_and_up",
      +  "250_to_500",
      +  "500_to_1000",
      +  "1000_and_up"
      +]
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/closed-world annotations, it discloses the return payload (item name, price band, reason, who it suits, affiliate link, guide link), the hard cap of 5 results, the important caveat that price bands are shown rather than live prices, and a mandatory verbatim disclosure string. That is the kind of behavior an agent cannot infer from the annotations.

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 usage condition is front-loaded, followed by return shape, the price-band caveat, the multi-band calling rule, and the disclosure requirement, in that order of importance. Every sentence carries an actionable instruction; nothing is filler.

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

Completeness5/5

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

There is no output schema, and the description compensates by enumerating the returned fields, the result cap, and the price-band limitation. Combined with the multi-call rule and required disclosure text, an agent has everything needed to invoke and present results correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: the concrete example that a $75-$150 budget spans 75_to_100 and 100_to_150 and requires one call per band, which clarifies how to compose budget_band beyond the schema's 'narrowest band' hint. It also implicitly ties the 'up to 5 picks' cap to the limit parameter's maximum.

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?

The description opens with a specific trigger and resource: gift ideas for a given budget and recipient, with example recipient types (employees, clients, law firm's clients). It also distinguishes itself from estimate_gift_budget by naming that tool as the prerequisite for amount-to-band conversion, so an agent can separate the two without reading schemas.

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?

It states the trigger clearly ('Use when someone wants gift ideas for a given budget and recipient') and gives an explicit procedural rule for multi-band budgets, plus routing to estimate_gift_budget when the user supplies a raw amount. It does not say when to prefer list_gift_guides or get_holiday_ship_by_dates instead, so the exclusion side is incomplete.

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