Skip to main content
Glama

Set a sealed team’s Force Disposition

set_event_team_disposition
Destructive

Chooses a Force Disposition the allied sealed lists offer before reveal. Use the Force Disposition id from the rules reference. 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>",
      "disposition": "<disposition>"
    },
    "name": "set_event_team_disposition"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
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
dispositionYes
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

A3.7/5.0
Behavior3/5

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

The annotations already disclose that this is a non-read-only, destructive, open-world operation, and the description adds the important timing constraint 'before reveal' plus the required permission. It does not explain whether an existing disposition is overwritten, whether the action is reversible, or what changes after reveal, so it adds only moderate behavioral context beyond annotations.

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

Conciseness5/5

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

The description is two compact sentences with the core purpose front-loaded and no unnecessary wording. Each sentence contributes either the action, the value source, or the permission requirement.

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 purpose, timing, permission, and one key parameter source. It remains incomplete about how the event/team is identified through eventToken and about the consequences of changing a sealed team's disposition.

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 description coverage is only 40%, and the description helpfully clarifies that the disposition value must be the Force Disposition id from the rules reference. However, it leaves the required token and the eventToken parameter unexplained, so it only partially compensates for the low schema coverage.

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 states a specific verb, 'Chooses,' and a specific resource, 'Force Disposition,' for allied sealed lists before reveal. It is clear what the tool does, but it does not explicitly distinguish itself from related setter siblings such as set_event_team_warlord.

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?

It gives useful usage context: the choice happens 'before reveal,' the value must come from the rules reference, and the caller needs 'mcp:manage.' These are clear prerequisites, but there is no explicit when-not guidance or named alternative tool.

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