Skip to main content
Glama

Get Original Item Gift Receipt

horizon_get_item_gift_operation
Read-onlyIdempotent

Reads one authorized gift or original sender receipt by operation ID to reconcile gift status and verify fee proof; read-only, no replacements or retries.

Instructions

Reads one authorized gift or the original own send receipt. Use when: explicit private item gift actions after reading horizon://docs/item-gifts. Claim offers and returns with horizon_claim_inbox. Not for: automatic gifting, polling or generated replacement operations. Use horizon_get_item_gift_operation to reconcile the original intent. Requires: userId and the player's session: sign in with horizon_signin_email or horizon_signin_anonymous and pass its accessToken as sessionToken. Side effects: Read only. Missing receipts never authorize replacement IDs; retained receipts never withdraw or charge again. Returns: {receipt,serverTime}; the receipt is the fee proof Errors: 409 REVISION_CONFLICT, OPERATION_CONFLICT, OPERATION_EXPIRED, STATE_CONFLICT and GIFT_EXPIRED, GIFT_DECLINED, GIFT_ALREADY_CLAIMED, GIFT_UNAVAILABLE need explicit reconciliation, never fresh revisions or operation IDs on an unknown outcome. Missing OPERATION_NOT_FOUND does not prove nonexecution. RECIPIENT_INBOX_FULL and 422 SELF_GIFT, ITEM_EQUIPPED, OPEN_GIFT_LIMIT_REACHED, GIFT_LIMIT_REACHED, INSUFFICIENT_BALANCE withdraw and charge nothing. 403 ITEM_GIFTS_DISABLED. 404 RECIPIENT_NOT_FOUND hides blocks. 429 ITEM_GIFTS_RATE_LIMITED schedules no retry. 401 means the session is missing or expired: sign in again and retry with the new accessToken. 403 for a session means the token belongs to another user: pass the userId that signed in. Needs HORIZON_API_KEY. Every failure returns an error result (isError) with the HTTP status and body: a 401 that horizon_test_connection also returns means HORIZON_API_KEY is wrong, 429 means the account's per-minute rate limit was reached (wait a minute, then retry).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "userId": "<userId>",
      "sessionToken": "<sessionToken>",
      "operationId": "<operationId>"
    },
    "name": "horizon_get_item_gift_operation"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesActive player matching the current session and project
operationIdYesOriginal canonical lowercase UUID
sessionTokenYesCurrent accessToken sent only as Bearer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.11.1

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds substantial behavior: auth chain (sign in via horizon_signin_email or horizon_signin_anonymous, pass accessToken as sessionToken, HORIZON_API_KEY required), a side-effect contract ('Missing receipts never authorize replacement IDs'), the return shape, and a rule that unknown outcomes must be reconciled rather than retried with fresh operation IDs. It also explains that generic 401/429 can be diagnosed via horizon_test_connection.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and labeled (Use when / Not for / Requires / Side effects / Returns / Errors), which aids scanning. But the error block is a dense run-on covering many codes plus generic 401/429/HORIZON_API_KEY boilerplate that repeats connection-level guidance, and the third-person self-reference is wasted text. It is over-stuffed for a single-UUID read.

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 read tool with no output schema, the description supplies the return shape ({receipt, serverTime}), the meaning of the receipt (fee proof), the auth prerequisites, and full error taxonomy including which failures are non-mutating and which require reconciliation. An agent has everything needed to call it and interpret an ambiguous outcome.

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 coverage is 100%, so the baseline is 3; the description goes beyond the schema by stating that sessionToken must be a sign-in accessToken and that userId must match the identity that signed in ('pass the userId that signed in'), which is real semantic linkage not present in the field descriptions. It does not explain why operationId must be the *original* canonical UUID beyond the schema's own wording.

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 opening sentence names a specific verb and resource: 'Reads one authorized gift or the original own send receipt,' scoped to a single operationId. It differentiates from horizon_claim_inbox and horizon_get_item_gift by pointing at reconciliation of an original intent rather than claiming or listing. However, the self-referential line 'Use horizon_get_item_gift_operation to reconcile the original intent' muddies the read-vs-reconcile framing, and the distinction from horizon_get_chat_operation / horizon_get_marketplace_operation (same getter family) is left implicit.

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?

Explicit 'Use when' and 'Not for' blocks name the alternative (horizon_claim_inbox) for claiming offers and returns, and exclude automatic gifting, polling, and generated replacements. The guidance is strong but the 'Use when' clause is thin — it conditions on reading horizon://docs/item-gifts rather than on a concrete selecting situation, and the 'not for polling' exclusion is confusing for a pure lookup tool.

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

Deploy Server

Other Tools