Skip to main content
Glama

Reopen a finished tournament table

reopen_tournament_table
Destructive

An organizer reopens a finished Swiss battle for score corrections, even if a later round has locked it. Use get_my_event with tableRound to find the battle token, then confirm the table. 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>",
      "battleToken": "<battleToken>"
    },
    "name": "reopen_tournament_table"
  }
}

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
battleTokenYes
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

A4/5.0
Behavior4/5

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

The annotations already declare a destructive, non-read-only, open-world mutation, and the description adds meaningful behavioral context: the action is for score corrections, can override a later-round lock, and requires mcp:manage. It does not fully explain what reopening changes about scores, pairings, or downstream state, but it substantially improves on the annotation profile.

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 tight sentences that front-load the action and scope, then follow with the lookup and permission requirements. There is no redundant wording or unnecessary background.

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?

It covers the core purpose, lock-override behavior, lookup path, and permission requirement, which is useful for a destructive mutation. However, given five parameters, low schema coverage, and no output schema, it should do more to clarify the token parameters and the consequences of reopening a table.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 40%, and the three core identifiers token, eventToken, and battleToken lack schema descriptions. The description partially compensates by explaining that battleToken can be found through get_my_event with tableRound, but it leaves token and eventToken unexplained and does not clarify the relationship between them. This is insufficient for a mutation with multiple required identifiers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: reopening a finished Swiss battle for score corrections. It also distinguishes the operation from ordinary reporting by noting it works even when a later round has locked the table. An agent can identify the intended action without opening the schema.

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 clear when-to-use context: an organizer correcting scores on a finished Swiss battle, including after a later round has locked it. It adds a concrete lookup procedure via get_my_event with tableRound and states the required mcp:manage permission. It does not explicitly name when not to use the tool or competing alternatives, so it falls short of a 5.

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