Skip to main content
Glama

Set a league round deadline

set_league_deadline
Destructive

A group organizer sets the deadline for one league round. Give milliseconds since the Unix epoch, or null to clear it. 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>",
      "deadline": "<deadline>"
    },
    "name": "set_league_deadline"
  }
}

Input Schema

NameRequiredDescriptionDefault
roundYes
tokenYes
deadlineYes
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 declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is supplied. The description adds context beyond them: the mcp:manage authorization requirement and the fact that passing null clears an existing deadline, which is precisely the destructive action the hint warns about. It stops short of saying what clearing does to an in-progress round or whether the change is reversible.

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?

Three short sentences, front-loaded with the action and resource, then the value format, then the permission gate. No filler or redundancy; every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A five-parameter mutation tool with no output schema, and the description covers the essential parts: who may call it, what it mutates, the units, and how to undo the value. It leaves out downstream effects of clearing a deadline (e.g., impact on pairings or clock behavior), which would be the remaining gap for a destructive write.

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

Parameters4/5

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

Schema description coverage is 40%, so the description must carry weight, and it does for the most ambiguous property: it specifies milliseconds since the Unix epoch and the meaning of null for deadline, which the schema only types as integer-or-null. 'One league round' ties the round parameter to a single round, though token and round themselves remain undocumented beyond bounds.

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?

States a specific verb and resource with scope ('sets the deadline for one league round') and names the actor ('a group organizer'), so the agent knows this is a scoped write on a single round rather than a league-wide clock. It does not explicitly contrast with plausible siblings such as set_tournament_round_timer or set_league_clock, leaving that differentiation to inference.

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?

Gives an implicit precondition ('A group organizer...' / 'Requires mcp:manage') and the accepted value format, which implies when the call is valid. It never states when to prefer this over set_tournament_round_timer for tournament rounds or set_league_clock for league-wide timing, and offers no exclusions.

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