Skip to main content
Glama

set group member role

horizon_set_group_member_role
DestructiveIdempotent

Sets a group member's role to officer or member using the exact reviewed group revision, helping leaders apply confirmed role changes without automatic retries after conflicts.

Instructions

Applies the explicit set group member role 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 sets another member's role to officer/member. 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
roleYesNew nonleader role for the target member
userIdYesSigned-in player matching the Bearer session
groupIdYesExact group UUID in the current project; never an authorization credential
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.3/5.0
Behavior5/5

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

Beyond annotations, it discloses the specific destructive effect (changing another member's role), no automatic retry, same-revision replay behavior, return shape, cache replacement guidance, and detailed error reconciliation paths. It is consistent with destructiveHint=true and idempotentHint=true.

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

Conciseness3/5

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

The description is organized with Use when/Not for/Requires/Side effects/Returns/Errors sections and is front-loaded, but it is very dense and run-on. Error and auth guidance is repeated enough that some sentences do not fully earn their place.

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 documenting the return shape, null group cases, cache behavior, auth requirements, and failure handling. For a destructive group-mutation tool, this gives an agent enough context to call and recover correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 adds useful meaning around sessionToken acquisition and expectedRevision caution, but it also mentions 'the exact pending requestId where applicable' even though no requestId parameter exists in the schema, creating potential confusion rather than fully clarifying parameters.

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 identifies the resource and operation through 'set group member role' and clarifies the effect as 'Leader sets another member's role to officer/member.' The opening 'Applies the explicit set group member role action' is somewhat abstract, but the side-effects line makes the actual operation clear and distinguishes it from siblings like transfer or remove member.

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?

It explicitly states when to use the tool: 'the player explicitly confirms this group action.' It also gives clear exclusions: not for replacing reviewed revisions/request IDs, bypassing a leader's block, or automatic retry after uncertainty. This is unusually strong routing guidance.

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