Skip to main content
Glama

Get Item Gift

horizon_get_item_gift
Read-onlyIdempotent

Retrieves one authorized item gift or original send receipt for a sender, recipient, or return owner using userId, giftId, and session token.

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: {gift,serverTime} for sender, recipient or return owner 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>",
      "giftId": "<giftId>"
    },
    "name": "horizon_get_item_gift"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.11.1

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered before the description starts. The description does add genuinely useful context beyond that: HORIZON_API_KEY and session requirements, the invariant that missing receipts never authorize replacement IDs, and that 429 schedules no retry. Against a declared annotation set, this is solid added context but not exhaustive behavior disclosure.

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?

It is front-loaded well, with purpose first and labelled sections (Use when / Not for / Requires / Side effects / Returns / Errors) that make scanning easy. However the Errors block is a dense wall of a dozen-plus codes, and 401/429 handling is stated twice in slightly different forms, which pushes length past what most readers will absorb in one pass.

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?

With no output schema, the explicit "Returns: {gift,serverTime}" line is necessary and present. For a read tool requiring session auth and carrying a large error surface (conflict, expiry, rate-limit, permission codes), the definition covers prerequisites, return shape, and failure semantics thoroughly enough for an agent to call it correctly.

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% and all three parameters are documented in the schema itself, so the baseline is 3. The description adds some cross-parameter meaning — sessionToken must be the accessToken from a sign-in call, and userId must match the session owner — but does not define giftId's semantics beyond what the schema's "Original canonical lowercase UUID" already states.

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?

The opening sentence gives a specific verb (Reads) and a precisely scoped resource: one authorized gift, or the original own send receipt. The scope qualifiers ("authorized", "own send receipt") distinguish it from list/claim siblings like horizon_get_item_gifts and horizon_claim_inbox without needing to open any schema.

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

Usage Guidelines5/5

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

The definition supplies an explicit "Use when" clause, an explicit "Not for" exclusion list (automatic gifting, polling, generated replacement operations), and names the concrete alternatives: horizon_claim_inbox for claiming and returns, and horizon_get_item_gift_operation for reconciling the original intent. That is the full when/when-not/alternative triad.

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