giftroam

Get order status

get_order_status

Read-onlyIdempotent

Customer-facing status, ETA window and next action for an order. Looked up by the buyer's private order token, issued after payment; the token is the only credential. Never returns address, phone or payment details.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`locale`	No	Language of the conversation with the user (e.g. he-IL, fr-FR). Localizes content and messages; prices and availability are unaffected.
`order_token`	Yes	The order token from the buyer's confirmation email (GR-XXXXX-…).

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
`status`	No	Machine status, e.g. confirmed \| on_the_way \| delivered \| needs_attention
`country`	No
`updated_at`	No
`next_action`	No
`display_text`	No	Human-readable one-line summary of the result
`status_label`	No
`delivery_date`	No
`estimated_window`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

changedInput schema / properties / order_token / description

Previous value: -"The order token from the buyer's confirmation (GR-XXXXX-…). Never guess tokens."New value: +"The order token from the buyer's confirmation email (GR-XXXXX-…)."

Changed2 schema fields changedAug 23, 2026

addedOutput schema / properties / estimated_window / properties

Added value: +{
+  "earliest": {
+    "type": "string"
+  },
+  "latest": {
+    "type": "string"
+  }
+}

changedOutput schema / properties / estimated_window / type

Previous value: -[
-  "string",
-  "null"
-]New value: +[
+  "object",
+  "null"
+]

First observedAug 21, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuinely new context beyond them: the token is the sole credential, and the response deliberately excludes address, phone and payment details — useful disclosure for an agent handling buyer data.

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 dense sentences, front-loaded with what the tool returns before moving to lookup mechanics and privacy guarantees. Every clause carries information; nothing is redundant or padded.

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?

With an output schema present, the description needn't document return values, and it correctly focuses on auth and privacy instead. The remaining gap is routing: nothing here disambiguates this tool from check_delivery or list_my_orders for an agent choosing among five siblings.

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 both parameters are already documented in the schema, making 3 the baseline. The description reinforces that order_token is a credential issued after payment, but adds no format or usage detail beyond what the schema's own descriptions provide (including for locale).

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 ('status, ETA window and next action for an order') and even scopes the audience as customer-facing, which is more than a bare restatement of the title. It does not, however, differentiate itself from siblings like check_delivery or list_my_orders, which an agent may plausibly confuse with this lookup.

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?

Gives clear preconditions for use: the order is looked up by the buyer's private order token, which is 'issued after payment' and is 'the only credential'. That tells an agent when the tool is callable. It stops short of the 5, since it names no alternative (e.g. check_delivery, list_my_orders) or exclusion condition.

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?