Skip to main content
Glama

Decline Friend Request

horizon_decline_friend_request
DestructiveIdempotent

Declines a specific incoming friend request using the reviewed player revision and exact request ID, preventing duplicate or unintended social actions.

Instructions

Declines Friend Request 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 and its exact requestId. Side effects: Removes only this exact incoming request and the matching sender outgoing record. 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
requestIdYesExact request ID from the reviewed incoming/outgoing snapshot
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.6/5.0
Behavior5/5

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

Adds substantial context beyond annotations: exactly what gets removed (this incoming request plus the sender's outgoing record), that repeating a revision cannot double-apply, that no automatic retry occurs, and that the full host/project/player cache should be replaced from the returned snapshot. It also documents rate limits (429), auth failure modes (401/403) and the HORIZON_API_KEY dependency with per-status remediation.

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?

Labeled sections (Use when, Not for, Requires, Side effects, Returns, Errors) make it easy to scan and front-load the decision-relevant information. Slightly redundant: the no-automatic-retry rule is stated twice, once under "Not for" and again under "Side effects," and the error block is dense.

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, revision-guarded mutation with five required parameters and no output schema, the description covers prerequisites, concurrency semantics, side effects, the returned snapshot shape and cache-replacement guidance, plus every meaningful error path. Nothing an agent needs to call it correctly is missing.

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 baseline is 3, but the description earns extra credit by explaining provenance and constraints: sessionToken comes from horizon_signin_email/horizon_signin_anonymous accessToken, expectedRevision must be the current snapshot revision, and requestId must be the exact ID from the reviewed snapshot. It also clarifies that a 403 means the wrong userId was paired with the token.

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 ("Declines Friend Request") and immediately scopes it to the exact incoming request via the reviewed revision. The side-effects sentence ("Removes only this exact incoming request and the matching sender outgoing record") implicitly separates it from horizon_cancel_friend_request and horizon_remove_friend without the agent needing the schema.

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" sections give clear inclusion and exclusion criteria, including the important anti-pattern of auto-retrying after a timeout. It stops short of naming the concrete sibling alternatives (horizon_cancel_friend_request for outgoing, horizon_accept_friend_request for acceptance), so routing is inferred rather than stated.

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