Skip to main content
Glama

Gift Genius

Find gift ideas

find_gift_ideas
Read-only

Get 9 personalized gift ideas for a specific person, each with a reason it fits and within the budget, plus one giftgenius.io link that opens the same ideas with photos and where to buy them. Pass every detail you already know about the recipient; only relationship, occasion and budget are required. Call again with "exclude" for more ideas.

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": {
      "relationship": "<relationship>",
      "occasion": "<occasion>",
      "budget": "<budget>"
    },
    "name": "find_gift_ideas"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoRecipient age in years, if known.
notesNoAnything else that helps: personality, things they already own, what to avoid (max 400 characters).
budgetYesPrice per gift: under-25 (under $25), 25-50, 50-100, or 100-plus ($100+). Ideas come from this tier or cheaper.
excludeNoNames of ideas already shown, to get 9 different ones. The most recent 45 are used.
occasionYesThe occasion. Use "Just because" if none fits.
interestsNoUp to 8 short interests or hobbies, e.g. ["coffee", "gardening"].
relationshipYesWho the gift is for. Map husband/wife/boyfriend/girlfriend to "Partner", son/daughter to "Kid", brother/sister to "Sibling", grandma/grandpa to "Grandparent", colleague to "Coworker"; otherwise "Someone else".

Output Schema

NameRequiredDescriptionDefault
noteNoShort advice for the giver.
ideasYes
list_urlNoThese same ideas on giftgenius.io, with photos and where to buy each one.
disclosureYes
finder_urlYesThe same search on giftgenius.io, for the user to refine or get more ideas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, open-world and non-destructive, but the description adds genuine substance: exactly 9 ideas, each with a fit reason, constrained to the budget tier, plus one external link. The 'call again with exclude' sentence explains why results are not idempotent, which aligns with idempotentHint=false.

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?

Three sentences, front-loaded with the output shape, then input guidance, then the pagination mechanism. No redundant or filler phrasing.

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?

Even with an output schema present, the description usefully frames what comes back and how to iterate. The only gap relative to sibling tools like find_hobby_gifts or check_gift_idea is the absence of routing guidance between them.

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 coverage is 100% with enum descriptions for relationship, occasion and budget, so the schema does the heavy lifting; the description only adds the 'pass every detail you already know' prompting and restates the exclude loop already documented in the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Get 9 personalized gift ideas for a specific person') and quantifies the output, including the reason-per-idea and the single giftgenius.io link. An agent immediately knows what this returns without opening the 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?

Gives clear operating context: pass every known detail, only relationship/occasion/budget are required, and re-invoke with 'exclude' for more ideas. It stops short of naming alternatives (e.g. find_hobby_gifts) or stating when a different sibling should be preferred.

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