giftroam

List my orders (signed-in)

list_my_orders

Read-onlyIdempotent

The signed-in user's GiftRoam orders: status, ETA window, gift, destination and the order token for tracking. Requires the authenticated GiftRoam connection (OAuth, scope orders:read); on a guest connection it returns auth_required. Never returns addresses, phone numbers or payment details.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`locale`	No	Language of the conversation with the user (e.g. he-IL, fr-FR). Localizes content and messages; prices and availability are unaffected.

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
`orders`	No
`display_text`	No	Human-readable one-line summary of the result

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 23, 2026
- addedOutput schema / properties / orders / items / properties / amount_minor
```
Added value: +{
+  "type": "number"
+}
```
- addedOutput schema / properties / orders / items / properties / created_at
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / orders / items / properties / currency
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / orders / items / properties / delivery_date
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / orders / items / properties / estimated_window
```
Added value: +{
+  "properties": {
+    "earliest": {
+      "type": "string"
+    },
+    "latest": {
+      "type": "string"
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / orders / items / properties / updated_at
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / orders / items / properties / url
```
Added value: +{
+  "type": "string"
+}
```
First observedAug 21, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive safety. Beyond that, the description discloses the required OAuth scope, the specific failure mode for guest connections (auth_required), and a privacy guarantee that addresses, phone numbers and payment details are never returned — useful behavioral context the annotations cannot express.

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: field inventory first, auth requirement second, privacy boundary third. No filler, no restatement of the title, and the most decision-relevant information (requires auth) is front-loaded after the payload summary.

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

Completeness4/5

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

An output schema exists so return shape need not be explained, and the description still covers auth, error behavior and privacy. The only shortfall is the absence of any hint about result volume or the limit parameter's effect on paging through a user's orders.

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 50%: locale is fully documented in the schema, limit is not. The description does not mention limit (default 20, max 50) or locale at all, but the limit bounds are largely self-describing and the locale semantics are already in the schema, leaving only a modest gap.

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 resource (the signed-in user's GiftRoam orders) and enumerates what each record carries: status, ETA window, gift, destination, tracking token. It does not, however, explicitly distinguish itself from the close sibling get_order_status, which an agent could confuse for a single-order variant of the same data.

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?

The description gives a clear precondition (authenticated OAuth connection with orders:read) and a negative case (guest connection returns auth_required), which is genuine routing guidance. It stops short of naming when to prefer this over get_order_status or check_delivery, so the agent must infer the multi-order scope itself.

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?