giftroam

Search gifts deliverable to a country

search_gifts

Read-onlyIdempotent

Find gifts that can be delivered to a destination country, optionally filtered by free text, occasion, budget (minor units) and a needed-by date. Returns a shortlist with final customer prices (delivery included) and delivery days. Paginate with cursor.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`query`	No	Product keywords, 1-4 words (e.g. 'chocolate basket', 'red roses'). Destination, recipient and occasion are separate fields. Omit for a general browse.
`cursor`	No	Opaque cursor from a previous page.
`locale`	No	Display language for results (e.g. he-IL). The query may be typed in that language.
`country`	Yes	Destination country, ISO-3166 alpha-2 (e.g. FR).
`occasion`	No	Occasion slug from the occasions resource (e.g. birthday).
`budget_max`	No	Maximum price in minor units (cents).
`budget_min`	No	Minimum price in minor units (cents).
`date_needed`	No	YYYY-MM-DD; only gifts that can arrive by then.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present only when the call failed
`total`	No
`locale`	No	BCP-47 locale the texts are localized to
`country`	No
`results`	No
`next_cursor`	No
`date_warning`	No	Present when the requested needed-by date is unreachable: results are shown WITHOUT the date filter
`display_text`	No	Human-readable one-line summary of the result

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

changedInput schema / properties / query / description

Previous value: -"Product keywords only, 1-4 words (e.g. 'chocolate basket', 'red roses'). Do NOT include the destination, recipient or occasion here - use the country/occasion fields. Omit for a general browse."New value: +"Product keywords, 1-4 words (e.g. 'chocolate basket', 'red roses'). Destination, recipient and occasion are separate fields. Omit for a general browse."

Changed8 schema fields changedAug 23, 2026
- addedOutput schema / properties / results / items / properties / contains_alcohol
```
Added value: +{
+  "description": "yes | no | unknown",
+  "type": "string"
+}
```
- addedOutput schema / properties / results / items / properties / currency
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / results / items / properties / customer_amount_minor
```
Added value: +{
+  "description": "Price in minor units (cents)",
+  "type": "number"
+}
```
- addedOutput schema / properties / results / items / properties / delivery_days / description
```
Added value: +"Business-day delivery estimate range"
```
- addedOutput schema / properties / results / items / properties / delivery_days / properties
```
Added value: +{
+  "max": {
+    "type": "number"
+  },
+  "min": {
+    "type": "number"
+  }
+}
```
- changedOutput schema / properties / results / items / properties / delivery_days / type
```
Previous value: -"number"New value: +"object"
```
- addedOutput schema / properties / results / items / properties / one_liner
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / results / items / properties / tags
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```

Changed1 schema field changedAug 21, 2026

addedOutput schema / properties / date_warning

Added value: +{
+  "description": "Present when the requested needed-by date is unreachable: results are shown WITHOUT the date filter",
+  "type": "string"
+}

First observedAug 21, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, but the description adds useful context: results include final customer prices with delivery and delivery days, and pagination uses a cursor. It does not cover auth or rate limits, so a 4 is appropriate.

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 tight sentences, front-loaded with the core action and relevant filters, then return shape, then pagination. Every sentence earns its place.

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 a rich input schema, annotations, and an output schema, the description need not explain return fields in depth; it still summarizes the shortlist and pagination. It covers the essential behavior for this search tool, so it is complete enough.

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 89%, so the schema already documents all nine parameters in detail. The description restates budget in minor units and the needed-by date but adds no format or syntax beyond the schema, so the baseline 3 applies.

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 opens with a specific verb and resource ('Find gifts') and scopes it to a destination country, with optional filter categories. It is clear what the tool does, though it does not explicitly differentiate itself from siblings like get_gift_details or check_delivery, so it falls short of a 5.

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?

It tells the agent that filters are optional and what dimensions can be filtered, implying the tool is for browsing/searching. It offers no when-to-use guidance relative to siblings such as check_delivery or get_gift_details, and no exclusions, so it remains at the implied-usage level.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All giftroam tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?