Skip to main content
Glama

Find gifts for a hobbyist

find_hobby_gifts
Read-only

Get up to 9 gift ideas for someone's hobby, pitched at their skill level (just curious, getting into it, obsessed), within the budget and skipping what they already own, plus a giftgenius.io link that opens the same ideas with photos and where to buy them. Also returns what someone at that level probably owns already. Pass what you know they own; the more specific, the better.

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": {
      "hobby": "<hobby>",
      "level": "<level>",
      "budget": "<budget>"
    },
    "name": "find_hobby_gifts"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoRecipient age in years, if known.
ownsNoWhat they already own for this hobby, brands and models if known (max 300 characters). Ideas skip these.
hobbyYesThe hobby, as specific as you know it, e.g. "home espresso", "pickleball", "watercolor painting".
levelYesHow into it they are: "curious" (just trying it), "getting-into-it" (has the basics, practicing regularly) or "obsessed" (deep into it, owns good gear).
budgetYesPrice per gift: under-25, 25-50, 50-100, or 100-plus. Ideas come from this tier or cheaper.
relationshipNoWho the gift is for, if known. 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
noteNoAn insider tip for the giver.
ideasYes
list_urlNoThese same ideas on giftgenius.io, with photos and where to buy each one.
page_urlNoGift Genius hobby page for this hobby, when there is one.
disclosureYes
finder_urlYesA search for this hobby on giftgenius.io, for the user to refine or get more ideas.
already_ownsYesWhat someone at this level likely already has (plus what was passed in "owns"): skip these.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuine behavioral detail on top: the result count cap of 9, the inclusion of a giftgenius.io link with photos and purchase locations, and the secondary return of what the recipient probably already owns. It is still silent on response shape beyond those hints, but with an output schema present that burden is reduced.

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 output is front-loaded with the core action and the count, then layers on constraints and the return extras. Sentences are dense but every one carries information; the only weakness is the slightly rambling third sentence about owned items.

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?

With an output schema available, the description need not detail return values, yet it still flags the link and the owned-items list, which are the surprising parts of the response. Six parameters at 100% schema coverage and simple annotations mean nothing an agent needs to invoke the tool correctly is missing.

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%, so all six parameters are already documented with enums and descriptions, which sets the baseline at 3. The description reinforces two of them ("skipping what they already own" for owns, the skill-level framing for level) but adds no syntax, format, or edge-case guidance the schema lacks, apart from the mild "the more specific, the better" nudge.

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 uses a specific verb and resource ("Get up to 9 gift ideas for someone's hobby") and scopes it by skill level, budget, and existing ownership, so the agent knows exactly what the tool produces. It does not, however, differentiate itself from the sibling find_gift_ideas, which on name alone sounds like it could serve the same request.

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?

Usage context is clear: this is the tool for hobby-based gift suggestions constrained by level, budget, and owned items, and it explicitly instructs "Pass what you know they own; the more specific, the better." There are no exclusions or named alternatives telling the agent when to prefer find_gift_ideas or get_gift_guide instead.

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