Skip to main content
Glama

Assign an event team

assign_event_team
Destructive

An organizer forms an allied side from two entrants, or sends one entrant id to separate them. Confirm all affected players before changing seats. Requires mcp:manage.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "token": "<token>",
      "userIds": "<userIds>"
    },
    "name": "assign_event_team"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
userIdsYes
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
eventTokenNo
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation risk is known; the description adds value by saying what is disrupted (player seats/sides) and by requiring a confirmation step plus the mcp:manage scope. It does not disclose failure behavior, reversibility, or what happens to a prior allied side when an entrant is separated.

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?

Three short sentences with the core effect front-loaded, followed by the safety caution and the permission requirement. 'Or sends one entrant id to separate them' is slightly awkward phrasing but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive five-parameter mutation with no output schema, the description covers the two operating modes, the confirmation requirement, and the permission scope. The significant remaining gap is event scoping: eventToken exists but the description never explains how the event is identified, nor does it describe the result of a successful call.

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 only 40%, so the description partially compensates by explaining that userIds carries either two entrant ids (forming a side) or one entrant id (separating), which is genuinely useful semantics beyond minItems/maxItems. However, token and eventToken are never mentioned, and the description never says how the target event is selected despite eventToken being a parameter.

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 gives a specific verb and effect: it 'forms an allied side from two entrants' or 'sends one entrant id to separate them', which tells an agent exactly what state change occurs. It is distinguishable in substance from siblings like set_event_team_disposition or set_event_team_warlord, though it never names them, so the differentiation is inferential rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Confirm all affected players before changing seats' is an operational caution rather than when-to-use guidance, and 'Requires mcp:manage' is an auth prerequisite. The description implies the organizer context but gives no explicit rule for choosing this tool over adjacent team-management siblings such as set_event_team_disposition or set_event_team_warlord.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources