Skip to main content
Glama

Report my table’s score

report_table_result
Destructive

Records the final score of the signed-in player's Swiss table, for a game not tracked on Praetorium, and finishes its battle; it counts for the tournament's standings but not the leaderboard. Report only a score both players agree. Defaults to your table this round. A result locks once the next round is paired; then only the organizer can reopen it. Requires mcp:write.

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>",
      "yourScore": "<yourScore>",
      "opponentScore": "<opponentScore>"
    },
    "name": "report_table_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
roundNoOmit for the current round.
tokenYesThe tournament or hidden-list game token, from list_my_events or its invite link.
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.
yourScoreYesYour victory points.
eventTokenNoeventToken from list_my_events; only an old link needs it.
missionPackIdNoA mission pack id from list_reference; omit for the current pack, as the site does.
opponentScoreYesYour opponent's victory points.
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. Changed2 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The 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.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The 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.",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: it explains that the result locks once the next round is paired, that only the organizer can reopen it afterward, that it requires mcp:write, and that it affects standings but not the leaderboard. That is exactly the mutation-lifecycle and permission context needed for a destructive, non-idempotent write.

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 with the core action and the most consequential constraint (locking) up front. The opening sentence is dense and packs scope, precondition, and effect together, but nothing is wasted.

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 eight-parameter write with no output schema, the description covers permissions, locking, and standings impact well. It leaves open what happens on a rejected or disputed score and gives no confirmation of what the call returns, but the calling essentials are present.

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 coverage is 100%, so parameter meaning is already carried by the schema. The description adds a little context by explaining the round default and table scoping, but says nothing about token, eventToken, llm_model, or conversation_id beyond what the schema states.

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?

States a specific verb and resource: records the final score of the signed-in player's Swiss table and finishes that battle. It also scopes the tool by excluding games tracked on Praetorium and clarifies the score feeds tournament standings but not the leaderboard, which separates it from battle-creation and report-reading siblings.

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 a clear usage condition ('a game not tracked on Praetorium', 'report only a score both players agree') and a default ('your table this round'). It implies an exclusion but never names the alternative tool an agent should use for tracked games, so routing is inferred rather than explicit.

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