Skip to main content
Glama

Report a league result

report_league_result
Destructive

A group organizer records a score for a game played outside Praetorium. Use the fixture key and scores in the exact seat order shown by get_league_fixtures. Confirm both player names and final scores. 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>",
      "fixture": "<fixture>",
      "vp": "<vp>",
      "missionPackId": "<missionPackId>"
    },
    "name": "report_league_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
vpYes
tokenYes
fixtureYes
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.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is known. The description adds the useful permission requirement and a confirmation step, but never says what is destroyed — whether an existing reported result is overwritten, whether the change is reversible, or how standings are affected. For a destructive write, that leaves the main behavioral question unanswered.

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 what and then the how, with no filler. The confirmation instruction and permission note each carry operational value.

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 mutation with no output schema and six parameters, the description covers the identity of the record, the data source, and the auth scope, which is a reasonable core. It still omits overwrite semantics, error conditions (e.g. fixture not found or already reported), and the meaning of missionPackId, so an agent cannot fully predict the outcome of a successful or failed call.

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 only 33%, so the description has to compensate and does so for the most error-prone field: it explains that vp must follow the exact seat order from get_league_fixtures, which the schema's array-of-two-integers does not convey. However, the required missionPackId, the token, and the relationship of 'both player names' to the fixture are left unexplained.

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: an organizer records a score for a league game played outside the system, with the 'league' scoping distinguishing it from the sibling report_table_result and report_tournament_table. The reliance on a fixture key from get_league_fixtures further pins down what kind of record it targets, though the description never names the sibling alternatives explicitly.

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 concrete preconditions: use the fixture key and seat ordering from get_league_fixtures, confirm both player names and final scores, and the caller needs the mcp:manage permission. It does not state when to prefer the table or tournament result siblings, so the routing guidance across the family is only implied.

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