Skip to main content
Glama

Set the tournament round timer

set_tournament_round_timer
Destructive

An organizer starts or stops the current round timer. Send minutes, or null to stop it. Use fromEnd only to add time to an existing deadline. 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>",
      "minutes": "<minutes>",
      "fromEnd": "<fromEnd>"
    },
    "name": "set_tournament_round_timer"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
fromEndYes
minutesYes
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

A3.9/5.0
Behavior4/5

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

The annotations already flag this as a destructive, non-read-only, open-world mutation. The description adds useful context beyond them: the mcp:manage permission requirement and the fact that null stops the timer. It does not say what happens to an in-progress round when the timer is stopped or reset, which is the main remaining behavioral gap.

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?

Four short sentences, each carrying a distinct rule, with the core action front-loaded. There is no filler and no repetition of the title.

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 mutation with six parameters and no output schema, the description covers the core semantics and the permission gate but omits the effect on an active round and the roles of the remaining parameters. It is adequate to invoke the tool correctly in the common case, but not complete.

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 33%, so the description must carry more weight. It does explain the two semantically important parameters, minutes and fromEnd, including the null-to-stop convention. It says nothing about token, eventToken, llm_model, or conversation_id, leaving half the 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 gives a specific verb and resource: an organizer starts or stops the current round timer. That is far more precise than the title alone. It does not, however, distinguish this tool from the nearby set_league_clock sibling, so an agent must infer the difference from the names.

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 states the two operating modes clearly: send minutes to start, or null to stop. It also constrains fromEnd to adding time to an existing deadline, which is a real usage rule. It gives no explicit when-not guidance or named alternative, 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