Skip to main content
Glama

Insolite Wow : idées cadeaux

Find gift ideas

find_gifts
Read-only

Search original, funny and unusual gift ideas. Describe the person or the occasion (e.g. "coffee lover dad", "white elephant", "cat owner") and optionally a budget. Returns up to 10 products with why they fit, a price range and the link to the product page (photos, current price and where to buy are on that page), plus gift guides on the same topic.

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": {
      "query": "<query>"
    },
    "name": "find_gifts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many products (default 6).
queryYesWho the gift is for, their interests or the occasion. Any language.
max_priceNoMaximum price in euros.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish this is a safe, read-only, closed-domain lookup, so the bar is lower. The description adds genuinely useful behavior: results are capped at 10, each item includes a fit rationale and price range, and photos/live price/purchase location live on the linked product page rather than in the response — an important expectation to set since there is no output schema.

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?

Two sentences, zero padding, and the core purpose is front-loaded ahead of the input guidance. Every sentence carries information an agent needs: what to send and what comes back.

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?

With no output schema and no enums, the description fully compensates by describing the return payload, its 10-item cap, and the pointer to product pages for prices and photos. Combined with annotations covering the safety profile, nothing essential is missing for correct invocation.

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 description coverage is 100%, so the baseline is 3; the schema already explains limit, query and max_price in euros. The description reinforces that the query is a free-form person/occasion description ("cat owner") and that budget is optional, adding mild framing value but no new syntactic or format guidance beyond the schema.

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 names a specific verb ("Search") and a specific resource ("original, funny and unusual gift ideas"), and the input model (describe a person or occasion) makes the tool's scope distinctive. It does not explicitly contrast itself with get_gift_guide or list_gift_guides, only mentioning that gift guides are also returned, so sibling differentiation is implied rather than stated.

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 gives clear invocation guidance: supply a description of the recipient or occasion, with concrete examples ("coffee lover dad", "white elephant", "cat owner") and an optional budget. It stops short of stating when NOT to use this tool or pointing to the sibling gift-guide tools for guide-only lookups.

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