Skip to main content
Glama

decline group request

horizon_decline_group_request
DestructiveIdempotent

Declines a specific pending group request using the reviewed group revision and request ID, applying the confirmed player action without automatic retry.

Instructions

Applies the explicit decline group request action using the reviewed group revision. Use when: the player explicitly confirms this group action. Not for: replacing reviewed revisions/request IDs, bypassing a leader's block, or retrying automatically after uncertainty. Requires: userId and the player's session: sign in with horizon_signin_email or horizon_signin_anonymous and pass its accessToken as sessionToken. Current group revision and the exact pending requestId where applicable. Side effects: Leader/officer declines this exact request. No automatic retry. Same-revision replay cannot create a second effect. Returns: {groups:MyGroupsView,group:GroupView|null}. groups is the actor's complete snapshot, never the target's private state. group is null after leave/delete; nonmembers never receive private data. Replace only the matching host/project/player cache. Errors: Use horizon_get_groups and horizon_get_group_pending to reconcile state. 409 REVISION_CONFLICT or uncertain response: read and reconcile intent, never refresh the revision and repeat automatically. Pending decisions require the original requestId; REQUEST_NOT_FOUND means it was removed/replaced. INBOX_FULL rolls back the entire action. 403 rejects group role, session or bilateral block violations. 429 is reported without automatic 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).

Input Schema

NameRequiredDescriptionDefault
userIdYesSigned-in player matching the Bearer session
groupIdYesExact group UUID in the current project; never an authorization credential
requestIdYesExact pending identity from the reviewed snapshot
sessionTokenYesPlayer accessToken, sent only in Authorization
targetUserIdYesOther player in this project
expectedRevisionYesExact reviewed revision; never replace automatically after an uncertain response

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: declares the leader/officer authority requirement, the no-automatic-retry rule, idempotent same-revision replay, the exact return shape ({groups, group|null}) and its privacy scoping, and specific error semantics (409 REVISION_CONFLICT, REQUEST_NOT_FOUND, INBOX_FULL rollback, 403 role/session/bilateral-block, 429, 401).

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 Use when / Not for / Requires / Side effects / Returns / Errors, so an agent can scan it quickly. It is dense and repeats itself in the error section (401 and 403 are each described twice, and HORIZON_API_KEY handling is restated at the end), which costs it a point.

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, stateful group mutation with six required parameters and no output schema, it supplies auth prerequisites, authority requirements, the return contract, privacy guarantees, cache-invalidation guidance, and a full error/recovery map. Nothing an agent needs in order to call it safely 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 adds real meaning: sessionToken must be the accessToken from horizon_signin_email/horizon_signin_anonymous, expectedRevision is the reviewed revision that must not be refreshed-and-retried, and requestId is the exact pending identity from a reviewed snapshot. It does not explain targetUserId or groupId beyond the schema.

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 ('decline group request ... using the reviewed group revision') and clarifies the actor: 'Leader/officer declines this exact request'. That distinguishes it from sibling operations like horizon_accept_group_request, horizon_cancel_group_request, and horizon_decline_group_invite without needing the 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?

Explicit 'Use when: the player explicitly confirms this group action' and 'Not for: replacing reviewed revisions/request IDs, bypassing a leader's block, or retrying automatically after uncertainty'. It also routes error recovery to horizon_get_groups and horizon_get_group_pending, naming the reconcile tools directly.

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