Skip to main content
Glama

Choose which allied Warlord leads

set_event_team_warlord
Destructive

Sets whose Warlord leads a side made from allied sealed lists. Use a teammate’s entrant id from get_my_event. 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>",
      "userId": "<userId>"
    },
    "name": "set_event_team_warlord"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
userIdYes
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, destructiveHint=true, and openWorldHint=true, so the agent knows this is a risky mutation. The description adds the mcp:manage authorization requirement, which is genuine context beyond the annotations, but it never explains what the destructive behavior entails, e.g. whether an existing Warlord assignment is overwritten or whether changes are reversible.

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, front-loaded with the action, then the data source, then the permission requirement. Nothing is padded, though the second sentence could be slightly tighter than 'Use a teammate's entrant id from get_my_event'.

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, open-world mutation with no output schema and five parameters, the definition covers the essentials an agent needs to attempt the call: source of the id and required permission. It is incomplete on overwrite/rollback semantics and on what the call returns, leaving the risk profile only partly described.

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?

With only 40% schema description coverage, the description should compensate more than it does. It clarifies the meaning of the userId-style parameter as a teammate entrant id sourced from get_my_event and hints that token is tied to the mcp:manage scope, but eventToken and the analytics fields (llm_model, conversation_id) go unmentioned.

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: setting which allied Warlord leads a side composed of allied sealed lists. That is clearly distinct from sibling mutation tools like set_event_team_disposition or assign_event_team, though it does not explicitly name a sibling it is not.

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?

It gives one concrete prerequisite – obtain a teammate's entrant id from get_my_event – and states the required mcp:manage scope, which is useful routing information. It stops short of saying when to prefer this over set_event_team_disposition or assign_event_team, so alternatives are only implied by the sibling naming.

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