Skip to main content
Glama

Assign a battlefield to a tournament table

set_tournament_table_battlefield
Destructive

An organizer chooses a layout from list_tournament_table_battlefields. Use roll to draw an allowed layout or null to let the players choose. 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>",
      "round": "<round>",
      "table": "<table>",
      "missionPackId": "<missionPackId>",
      "battlefield": "<battlefield>"
    },
    "name": "set_tournament_table_battlefield"
  }
}

Input Schema

NameRequiredDescriptionDefault
roundYes
tableYes
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
battlefieldYes
missionPackIdYes
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; the description adds the useful auth detail 'Requires mcp:manage'. However, for a destructive mutation it never says what is overwritten (e.g., an existing battlefield assignment being replaced) or whether the change is reversible, which is exactly the context annotations cannot convey.

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?

Two short sentences, with the layout source and the battlefield value semantics front-loaded before the permission note. No filler, though the permission requirement is tacked on without context about failure behavior.

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 an 8-parameter destructive write with no output schema, the definition covers the battlefield argument and auth but omits overwrite semantics, error/permission-failure behavior, and the meaning of round/table/missionPackId scoping. An agent could call it, but not confidently predict what it replaces.

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 25% schema description coverage across 8 parameters, the description should carry more weight; it does explain the key battlefield parameter's three shapes (layout object, 'roll', null) more meaningfully than the schema does. It adds nothing about round, table, missionPackId, token, eventToken, llm_model, or conversation_id, leaving most parameters undocumented in both places.

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 conveys the effect (choosing/assigning a layout to a tournament table) and points at list_tournament_table_battlefields as the source of valid layouts, so an agent can distinguish it from the read-only sibling. It never states the tool's own verb directly — the operation is described from the organizer's point of view ('An organizer chooses a layout') rather than as 'assigns a battlefield to table N in round R' — leaving the exact write target slightly implicit.

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 conditional guidance for the battlefield argument ('roll' to draw, null to let players choose) and states the mcp:manage permission requirement. It does not say when to prefer this over related siblings like swap_tournament_table_seats or reopen_tournament_table, nor does it state preconditions such as whether the table must already exist or the round be paired.

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