Skip to main content
Glama

Set the league chess clock

set_league_clock
Destructive

A group organizer sets the chess-clock minutes for league games that have not started, or null to clear the limit. 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>"
    },
    "name": "set_league_clock"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
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.
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?

Annotations already flag the tool as destructive and open-world, but the description adds the authorization requirement ('Requires mcp:manage') and clarifies that null clears the limit. It does not say what happens if a game has already started or what errors look like, leaving some gaps around this destructive operation.

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?

Two tight sentences pack the actor, scope, value semantics, and auth requirement. There is no padding or repetition, and the core action is front-loaded.

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, four-parameter tool with no output schema, the description covers scope, auth, and null semantics well. It still leaves open what happens when the precondition is violated and what the minutes value applies to per player versus the whole game, which matters for correct invocation.

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 50%, so the description must carry weight. It does explain that the minutes value is the chess-clock limit and that null clears it, which adds real meaning beyond the numeric range in the schema. It says nothing about the token parameter beyond the auth hint, so compensation is partial.

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 uses a specific verb and resource: 'sets the chess-clock minutes for league games'. The scope qualifier 'league games that have not started' makes the target explicit. It is distinct enough from the tournament variant, though it does not name that sibling outright.

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?

The description gives clear preconditions for use: an organizer with mcp:manage, and only games not yet started. It also explains how to clear the limit ('null'). It does not, however, name an alternative tool or explicitly rule out changing clocks on in-progress or finished games.

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