Skip to main content
Glama

Update a tournament or hidden-list game

update_event
Destructive

An organizer changes settings or schedule. Read get_my_event first. If changing tournament details, send the name, description, visibility, admission and player limit together. 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>"
    },
    "name": "update_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
ruleNo
tokenYes
scheduleNo
admissionNo
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.
visibilityNo
descriptionNo
playerLimitNo
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.
clockLimitMinutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is known; the description usefully adds the mcp:manage scope requirement and a read-before-write precondition. However, it never says what a destructive update actually destroys or whether omitted fields are preserved versus reset — the single most important behavioral fact for a partial-update mutation.

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?

Four short sentences, front-loaded with the actor and effect, then prerequisites, then the batching instruction and auth scope. Nothing is redundant, though the telegraphic phrasing ('Read get_my_event first. If changing tournament details...') makes the flow slightly staccato.

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

Completeness2/5

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

For an 11-parameter, nested-object, destructive mutation with no output schema, the description covers only the top-level identity fields and omits the whole rule/scoring configuration and time limit. An agent could plausibly invoke it but would be guessing about game-rule payloads and about replace-versus-merge semantics.

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 18% across 11 parameters, so the description must carry the burden, and it names just five fields plus the notion of 'schedule'. The large nested `rule` object, clockLimitMinutes, and the required `token` are given no semantic explanation in the description, leaving most of the payload to be inferred from the raw schema.

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 scope: an organizer changes 'settings or schedule' of an existing event, and the title narrows the resource to a tournament or hidden-list game. It is clear what the tool does, though it does not explicitly contrast itself with create_tournament or update_group beyond the prerequisite pointer to get_my_event.

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?

Gives actionable when-to-use guidance: read get_my_event first, and when editing tournament details send name/description/visibility/admission/playerLimit together so the change is coherent. It also states the authorization requirement (mcp:manage). No explicit when-not-to-use or alternative for schedule-only versus settings-only edits.

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