Skip to main content
Glama

delete group

horizon_delete_group
DestructiveIdempotent

Deletes a group using its reviewed revision after explicit player confirmation, only when no invitations or requests remain; no automatic retry after uncertain responses.

Instructions

Applies the explicit delete group 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: Sole leader deletes the group only when no invitations/requests remain. 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
sessionTokenYesPlayer accessToken, sent only in Authorization
expectedRevisionYesExact reviewed revision; never replace automatically after an uncertain response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.9.1

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description adds real value: sole-leader precondition, the no-invitations/requests-remaining gate, no automatic retry, and same-revision replay producing no second effect. Auth path (sign in, pass accessToken as sessionToken), rate-limit behavior, and full error taxonomy are all disclosed.

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) front-load the action and make it scannable, which is the right structure for a destructive tool. It is on the verbose side, with 401/403 handling restated in both the Errors and the trailing paragraph, costing some density.

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?

There is no output schema, and the description compensates by specifying the return shape ({groups: MyGroupsView, group: GroupView|null}) plus the rule that groups is the actor's snapshot and never the target's private state. Error reconciliation steps, cache-replacement scope, and API-key failure modes are all covered, leaving nothing an agent needs to call this safely.

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 operational meaning: sessionToken must come from horizon_signin_email/horizon_signin_anonymous, and expectedRevision must never be refreshed and blindly retried after an uncertain response. That is semantic guidance beyond the field text, though it doesn't explain groupId versus any other identifier beyond what the schema says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("delete group action") and pins the mechanism to a reviewed group revision, which an agent can act on unambiguously. It stops short of naming the closest sibling (horizon_leave_group) that a player-vs-leader distinction should route away from, so the differentiation is implied by the side-effects clause rather than stated.

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: the player explicitly confirms this group action" and a "Not for:" list covering revision replacement, block bypass, and automatic retry. The exclusions target retry/state misuse rather than naming the sibling alternative (horizon_leave_group, horizon_transfer_group_leadership), so it falls short of full alternative routing.

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