Skip to main content
Glama

Pick a Secret Santa gift

pick_secret_santa_gift
Read-onlyIdempotent

Filters Santa's vetted 212 hand-checked gift ideas - the Secret Santa subset of the shared 255-idea bank it shares with its sister site The Present Picker, sorted here for Secret Santa by the budget band your group agreed for its draw - with strict parameters, and returns up to three picks. Parameters: budget_band (required: under_25, 25_to_50, 50_to_100, over_100); recipient_type (anyone, kid - only ideas from the bank's Kid shelf, or adult - everything except the Kid shelf); one interest hint (books, cooking, cozy, fitness, games, gardening, music, outdoors, science, tech, travel, or surprise) which ranks matches first; and avoid, a list of words - any idea whose name, blurb, or why mentions an avoid word is excluded, and the answer says how many ideas the filters set aside. Each pick names the kind of gift, why it fits, and what to look for and avoid. No brands, no stores, no exact prices: budget bands are guides, not exact prices. This tool never asks who the gift is for by name and knows nothing about any draw.

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

Input Schema

NameRequiredDescriptionDefault
avoidNoWords to exclude: any idea whose name, blurb, or why mentions one of these words is filtered out (for example "coffee" or "scented").
budgetNoLegacy alias for budget_band.
interestNoOne interest hint for the person, or surprise for any.
budget_bandNoThe group's budget band.
recipient_typeNoWho the gift is for: kid returns only the bank's Kid-shelf ideas; adult excludes them; anyone (default) applies no recipient filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral detail beyond that: results are capped at three, the response reports how many ideas the filters set aside, budget bands are guides rather than exact prices, and no brands, stores, or prices appear. That is meaningful context an agent cannot get 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core action, but the opening sentence is an overstuffed parenthetical about 212 versus 255 ideas and the sister site The Present Picker, which is not operationally useful. The parameter enumeration is dense but scannable. Trimming the catalog-marketing details would make the definition materially tighter.

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

Completeness3/5

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

Given no output schema, the description does well to describe the shape of each pick and the filtered-out count. But for a five-parameter tool it leaves the legacy 'budget' alias undocumented and misstates which parameter is required, which are the main gaps a calling agent would hit.

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 the baseline is 3, and the description does add value by explaining that the interest enum ranks matches first and that avoid matches against name, blurb, or why rather than title only. However, it omits the 'budget' legacy alias entirely and declares budget_band 'required' while the schema lists no required properties, which can mislead an agent about how to call the tool.

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?

States a specific verb and resource: filters a curated Secret Santa gift bank and returns up to three picks, each with a kind, a why, and what to look for. That is clearly distinguishable from the sibling tools (explain_secret_santa_rules, plan_secret_santa_setup), though the description never names or contrasts them explicitly. The core action is buried after a long parenthetical about the sister site and idea counts, slightly diluting clarity.

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?

Usage is implied rather than stated: it is the gift-selection step after a budget band has been agreed. There is no explicit when-to-use versus the setup or rules-explainer siblings, and no stated prerequisite (e.g., run plan_secret_santa_setup first). The closing line 'never asks who the gift is for by name and knows nothing about any draw' usefully bounds what the agent should not rely on it for.

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.