Skip to main content
Glama
ProjectMakersDE

horizOn MCP Server

Official
by ProjectMakersDE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Unblock Player

horizon_unblock_player
DestructiveIdempotent

Unblock a player using the reviewed snapshot revision to remove only your block without restoring friendship or affecting the other player's block.

Instructions

Unblocks Player using the reviewed player revision. Use when: the player explicitly requests this social action. Not for: automatic retries after timeout, automatic acceptance of crossed requests or changing expectedRevision without reconciling intent. Requires: userId and the player's session: sign in with horizon_signin_email or horizon_signin_anonymous and pass its accessToken as sessionToken. A current snapshot revision. Side effects: Removes only your block. Does not restore a friendship or request, and does not remove the other player's block. No automatic retry. Repeating the same revision cannot create a second effect. Returns: Complete {userId,revision,friendCode,friends,incoming,outgoing,blocked,limits,serverTime} snapshot. Replace the matching host/project/player cache. lastActiveAt is the latest retained login, null when unknown; it is not online presence. Errors: 409 REVISION_CONFLICT or an uncertain response: get a new snapshot and reconcile intent, never silently replace expectedRevision and repeat. 404 FRIEND_REQUEST_NOT_FOUND means this request was removed or replaced; do not act on a newer ID. INBOX_FULL rejects the entire send/accept. Friend/request/block capacity limits reject additions while existing data remains removable. 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).

Input Schema

NameRequiredDescriptionDefault
userIdYesSigned-in player UUID matching the session
sessionTokenYesPlayer accessToken sent only as Authorization Bearer
targetUserIdYesThe other player UUID in the same project
expectedRevisionYesExact revision from the reviewed actor snapshot; never refresh and substitute automatically

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.1

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that only your block is removed, the other player's block persists, no friendship is restored, and that replaying the same revision cannot produce a second effect (consistent with idempotentHint=true). It also documents auth prerequisites, rate limiting (429), and a full error taxonomy (409/404/INBOX_FULL/401/403/needs HORIZON_API_KEY).

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

Conciseness4/5

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

Front-loaded with a one-line purpose, then clearly labeled Use when / Not for / Requires / Side effects / Returns / Errors sections, so it is scannable despite its length. Some of the error prose is dense and slightly repetitive around the 401/HORIZON_API_KEY distinction, keeping it short of a 5.

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 destructive, state-mutating call with no output schema, the description supplies everything an agent needs: required credentials, the returned snapshot shape and that it should replace the cache, the meaning of lastActiveAt, and recovery paths for every enumerated failure. Nothing material is left to inference.

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 earns extra by explaining how to obtain sessionToken (sign in via horizon_signin_email/horizon_signin_anonymous and pass the accessToken) and by framing expectedRevision as coming from a reviewed snapshot that must be reconciled, not refreshed. It does not add per-parameter detail for targetUserId beyond what the schema already says.

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 ("Unblocks Player") and immediately scopes the mechanic: it removes only the caller's block and does not restore a friendship or request. This distinguishes it from the sibling horizon_block_player and from horizon_remove_friend without needing either 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?

Explicit "Use when" (player explicitly requests this social action) and "Not for" (automatic retries after timeout, automatic acceptance of crossed requests, silently changing expectedRevision). The positive trigger and the exclusions are both named, so an agent can route between this and the block/friend tools.

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