giftroam

Create a checkout link

create_checkout

Idempotent

Create a signed, single-purpose checkout link (30-minute expiry) for one gift to one country. The schema has no recipient fields on purpose: name, address, phone, delivery details and payment are collected on the secure page. Returns an order summary with the link. Retries with the same idempotency_key return the same link.

Input Schema

TableJSON Schema

Name	Required	Description
`locale`	No	Language of the conversation with the user (e.g. he-IL, fr-FR). Localizes content and messages; prices and availability are unaffected. The checkout page opens in this language.
`country`	Yes	Destination country, ISO-3166 alpha-2.
`gift_id`	Yes	A gift_id from search results.
`quantity`	No	Always 1 in v1.
`delivery_date`	No	Requested delivery date YYYY-MM-DD; omit for as-soon-as-possible.
`gift_card_text`	No	Card message (≤180 chars) if the user already gave one.
`idempotency_key`	Yes	Client-generated key; retries with the same key return the same link.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present only when the call failed
`locale`	No	BCP-47 locale the texts are localized to
`summary`	No
`expires_at`	No
`checkout_url`	No	Single-purpose secure checkout link on checkout.giftroam.com (30-minute expiry)
`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."New value: +"A gift_id from search results."

Changed2 schema fields changedAug 23, 2026
- addedOutput schema / properties / summary / properties / estimated_window / properties
```
Added value: +{
+  "earliest": {
+    "type": "string"
+  },
+  "latest": {
+    "type": "string"
+  }
+}
```
- changedOutput schema / properties / summary / properties / estimated_window / type
```
Previous value: -"string"New value: +"object"
```
First observedAug 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Adds substantial context beyond the annotations: the link is signed, single-purpose, and expires in 30 minutes; recipient fields are deliberately absent; and the response includes an order summary. Annotations already cover idempotency and read/write hints, but the description usefully clarifies the expiry and security model.

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?

Four tightly written sentences, front-loaded with the core action and constraints; every sentence carries distinct information (scope, omission rationale, return value, idempotency) with no repetition.

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?

For a 7-parameter mutation tool with full schema coverage, an output schema, and rich annotations, the description covers the remaining gaps (expiry, no-recipient design, return shape, retry semantics). Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description adds meaning by explaining that recipient/address/payment fields are intentionally omitted and collected on the secure page, which prevents an agent from inventing or expecting those parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Create) and resource (signed, single-purpose checkout link) with clear scope: one gift to one country, 30-minute expiry. This distinguishes it cleanly from read-oriented siblings like search_gifts and get_gift_details.

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?

Explains the retry contract (same idempotency_key returns the same link) and implicitly routes the agent to gather recipient/payment data on the hosted page rather than via parameters. It does not explicitly name alternative tools or state when not to call it, so it falls short of a 5.

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?