giftroam

Get gift details

get_gift_details

Read-onlyIdempotent

Full description, contents, images, customer price, estimated delivery window (EST cutoff-aware), substitution policy and restrictions for one gift in one destination country.

Input Schema

TableJSON Schema

Name	Required	Description
`locale`	No	Display language for gift content (e.g. he-IL). Prices and availability are unaffected.
`country`	Yes	Destination country, ISO-3166 alpha-2.
`gift_id`	Yes	A gift_id from search results (or the gift's URL slug).

Output Schema

TableJSON Schema

Name	Required	Description
`gift`	No
`error`	No	Present only when the call failed
`locale`	No	BCP-47 locale the texts are localized to
`translation`	No	How the gift content was localized
`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 / gift_id / description

Previous value: -"gift_id from search_gifts (or the gift's URL slug)."New value: +"A gift_id from search results (or the gift's URL slug)."

Changed12 schema fields changedSep 23, 2026

addedOutput schema / properties / gift / properties / contains_alcohol

Added value: +{
+  "description": "yes | no | unknown",
+  "type": "string"
+}

addedOutput schema / properties / gift / properties / currency
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / gift / properties / customer_amount_minor

Added value: +{
+  "description": "Price in minor units (cents)",
+  "type": "number"
+}

addedOutput schema / properties / gift / properties / delivery_days

Added value: +{
+  "description": "Business-day delivery estimate range",
+  "properties": {
+    "max": {
+      "type": "number"
+    },
+    "min": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / gift / properties / display_price / description
```
Added value: +"Final customer price incl. delivery, e.g. \"$99.95\""
```

addedOutput schema / properties / gift / properties / estimated_delivery

Added value: +{
+  "properties": {
+    "cutoff_passed_today": {
+      "type": "boolean"
+    },
+    "earliest": {
+      "type": "string"
+    },
+    "latest": {
+      "type": "string"
+    },
+    "notes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / gift / properties / image_url
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / gift / properties / one_liner
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / gift / properties / substitution_policy
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / gift / properties / tags

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / gift / properties / url
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / translation

Added value: +{
+  "description": "How the gift content was localized",
+  "properties": {
+    "contentHash": {
+      "type": "string"
+    },
+    "provider": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sourceLocale": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    },
+    "targetLocale": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedAug 21, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds one genuine behavioral nuance — the delivery window is 'EST cutoff-aware' — which is not derivable from annotations, but otherwise it discloses nothing beyond the return payload.

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?

A single compact sentence with no filler, front-loaded on the resource. It spends its whole budget on output inventory that the output schema already supplies, which is a mild structural misallocation rather than verbosity.

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?

With an output schema present, enumerating return fields was not strictly necessary, and the description omits the one thing an agent actually needs — when this lookup is the right call versus search_gifts. Annotations plus schema cover safety and parameters, so the gap is narrow but real.

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 three parameters (gift_id, country, locale) are fully documented in the schema, including locale's display-only effect. The description adds only 'one destination country'; baseline 3 applies since the schema does the heavy lifting.

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+resource: retrieve details for 'one gift in one destination country', and enumerates the payload (description, contents, images, price, delivery window, substitution policy). The scope contrasts implicitly with search_gifts, but no sibling is named, so an agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description is entirely a return-value inventory; it says nothing about when to call this versus search_gifts or check_delivery, nor that gift_id must come from a prior search. Only the schema's gift_id description hints at provenance, so usage is effectively unguided.

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?