Skip to main content
Glama

Get Own Item Gifts

horizon_get_item_gifts
Read-onlyIdempotent

Retrieves a player's bounded sent item gifts, open received offers, and recent gift history to support explicit gift actions and reconciliation.

Instructions

Reads the own bounded lists of sent gifts, received open offers and recent history. 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. No automatic refresh or polling. Returns: {state:{userId,revision,sent,history,received,operationWindow,limits},serverTime} 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>"
    },
    "name": "horizon_get_item_gifts"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, it discloses that there is no automatic refresh or polling, documents the full failure taxonomy (409/422/403/404/429/401 with per-code meaning), and notes the HORIZON_API_KEY dependency. It also adds a genuinely important caveat that OPERATION_NOT_FOUND does not prove non-execution and that conflict outcomes require reconciliation rather than fresh IDs.

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?

Labeled sections (Use when / Not for / Requires / Side effects / Returns / Errors) make it front-loaded and scannable, but the error block is a dense run-on that repeats itself: 401 is explained twice and 429 is described twice. It also contains internal tension, saying the rate-limit error 'schedules no retry' while the closing line says to wait and retry.

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?

No output schema exists, and the description compensates by giving the exact return shape plus a comprehensive error contract and authentication requirements. For a two-parameter read tool, an agent has everything needed to call it and interpret failures.

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, but the description adds real meaning: sessionToken is the accessToken from horizon_signin_email/horizon_signin_anonymous, and userId must be the identity that actually signed in (called out in the 403-for-session error). That goes beyond the schema's 'Active player matching the current session' phrasing.

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 and resource set: reads bounded lists of sent gifts, received open offers and recent history. It also scopes the tool explicitly against named relatives (horizon_claim_inbox for claims/returns, horizon_get_item_gift_operation for reconciliation), so an agent can pick it without opening schemas.

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?

Provides an explicit 'Use when' clause, an explicit 'Not for' exclusion list (automatic gifting, polling, generated replacement operations), and names the alternative tools for the excluded cases. Prerequisites for getting the required session are also spelled out, leaving nothing to inference.

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