Skip to main content
Glama

Get Item Gift Configuration

horizon_get_item_gift_config
Read-onlyIdempotent

Checks whether item gifting is enabled and returns the fixed sender fee, currency, and configured limits before a private item gift action. Use it to confirm gift availability and costs.

Instructions

Reads whether gifting is enabled, the fixed sender fee with its currency and the configured limits. 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: {config:{revision,enabled,currencyKey,fee},limits,serverTime}; currencyKey null means a free gift 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_gift_config"
  }
}

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

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnly/idempotent/openWorld), it discloses auth prerequisites (userId plus sessionToken obtained from horizon_signin_email or horizon_signin_anonymous), HORIZON_API_KEY requirements, a rate-limit behavior (429, no retry), and status semantics including that 404 RECIPIENT_NOT_FOUND hides blocks and that failures return isError with status and body. Much of the error taxonomy (SELF_GIFT, INSUFFICIENT_BALANCE, GIFT_ALREADY_CLAIMED, withdraw/charge semantics) is irrelevant to a pure read and dilutes the useful disclosure.

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

Conciseness2/5

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

Purpose is front-loaded and the labeled blocks are scannable, but the description is a sprawling error dump for a two-parameter read tool, spending most of its length on gift-mutation outcomes (charges, claims, declines) that cannot occur here. Large portions do not earn their place relative to the single read operation.

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 no output schema, the description compensates by spelling out the return shape {config:{revision,enabled,currencyKey,fee},limits,serverTime} and the null-currencyKey meaning a free gift, plus auth, rate-limit, and failure semantics. It is close to complete for this complexity; the only real hole is that sequencing relative to sending a gift is left implicit.

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 further by explaining how to obtain sessionToken (sign in first, pass the accessToken) and by tying 401 handling back to re-authentication and 403 to a userId mismatch. That is meaningful operational meaning the schema's one-line parameter strings do not convey.

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 names a specific verb (reads) and enumerates exactly what is read: whether gifting is enabled, the fixed sender fee with its currency, and the configured limits. An agent can tell this apart from horizon_get_item_gift_operation or horizon_send_item_gift without inspecting their schemas.

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?

It does supply a "Use when" / "Not for" split with named alternatives (horizon_claim_inbox, horizon_get_item_gift_operation) and excludes polling and automatic gifting. However, the stated use case ("explicit private item gift actions") describes gift actions rather than reading configuration, so the obvious primary trigger — call this before sending a gift to learn the fee and limits — is never stated and the guidance reads as boilerplate reused across the gift family.

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