Skip to main content
Glama

Report a tournament table score

report_tournament_table
Destructive

An organizer reports a score for a tournament table. Obtain the round, table and seat order from get_my_event. Confirm both players and scores, then pass those same player IDs in expectedPlayers. Players at the table can use report_table_result instead. 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>",
      "table": "<table>",
      "missionPackId": "<missionPackId>",
      "vp": "<vp>",
      "expectedPlayers": "<expectedPlayers>"
    },
    "name": "report_tournament_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
vpYes
roundYes
tableYes
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
missionPackIdYes
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.
expectedPlayersYesThe two player IDs in seat order from get_my_event.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/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 mutation profile is known. The description adds genuinely non-structured context: the mcp:manage scope requirement and the expectedPlayers guard, which implies the call is validated against the current seating. It does not say what happens to an already-reported score or how a mismatch fails, leaving a small gap for a destructive write.

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, front-loaded with the action, then prerequisites, then the alternative, then the permission gate. Nothing is redundant and no sentence could be dropped without losing guidance.

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?

For a destructive, nine-parameter organizer tool with no output schema, the description covers the workflow, the identity guard, the sibling alternative and the auth scope. It stops short of describing conflict behavior when expectedPlayers no longer matches the table or whether an existing report is overwritten, which would matter 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 coverage is only 33%, so the description must compensate, and it does for the two riskiest fields: expectedPlayers is defined as 'the two player IDs in seat order from get_my_event', and the 'confirm both players and scores' instruction implies vp is a paired, seat-ordered score list. Undocumented fields such as token, eventToken, missionPackId and the analytics params get no help here, but they are largely mechanical.

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 first sentence names a specific verb and resource ('An organizer reports a score for a tournament table'), and the last-but-one sentence explicitly routes players to the sibling tool report_table_result. An agent can distinguish this organizer-only path from the player path without inspecting either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit prerequisite chain ('Obtain the round, table and seat order from get_my_event. Confirm both players and scores'), names the alternative ('Players at the table can use report_table_result instead'), and states the permission requirement ('Requires mcp:manage'). When-to-use, when-not-to-use, and required authorization are all present.

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