Skip to main content
Glama
Sign In

Whistle.day - Tournament organizer

by day.whistle
OverviewDiscussionsAdmin

update_fixture

Destructive

Update a fixture's score and status (settle a match)

Input Schema

NameRequiredDescriptionDefault
idYesFixture ID
courtNoCourt ID (optional)
statusYesNew status: finished, walkover, live, ready, pending
winnerNoWinner entry ID (for walkover)
away_scoreNoAway score
home_scoreNoHome score

Output Schema

NameRequiredDescriptionDefault
idYesRecord ID
codeYesShort handle for the match, e.g. A1 or QF2
statusYesStatus
winnerYesEntry ID of the winner, empty until decided
away_scoreYesAway score: sets, or goals
home_scoreYesHome score: sets, or goals

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "away_score": {
+      "description": "Away score: sets, or goals",
+      "type": "integer"
+    },
+    "code": {
+      "description": "Short handle for the match, e.g. A1 or QF2",
+      "type": "string"
+    },
+    "home_score": {
+      "description": "Home score: sets, or goals",
+      "type": "integer"
+    },
+    "id": {
+      "description": "Record ID",
+      "type": "string"
+    },
+    "status": {
+      "description": "Status",
+      "type": "string"
+    },
+    "winner": {
+      "description": "Entry ID of the winner, empty until decided",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "code",
+    "status",
+    "home_score",
+    "away_score",
+    "winner"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / properties / session_token
      Removed value: -{
-  "description": "The session_token returned by create_tournament",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "id",
-  "status",
-  "session_token"
-]New value: +[
+  "id",
+  "status"
+]
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, non-idempotent, non-readOnly, so safety profile is covered by structured data. The description adds little beyond what annotations provide, though 'settle a match' hints at finality. It does not explain reversibility or what data a status change affects.

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?

A single front-loaded sentence with zero waste. Every word earns its place and the main action is stated first.

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?

The tool is a mutation with subtle implications (settling a match changes tournament standings and stage progression), yet the description does not mention downstream effects or whether the fixture must be in a particular state. With an output schema present, return values need not be explained, but the behavioral context for a destructive update is thin.

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 all six parameters are already documented in the schema, including status enum values and winner semantics for walkover. The description only names 'score and status' generically, adding no syntax or format detail beyond the schema baseline.

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 (update) and resource (fixture) with the fields ('score and status') and an example motivation ('settle a match'). It does not name the sibling get_fixture as the read alternative, but the purpose is clear enough to distinguish from list/get tools.

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?

The parenthetical 'settle a match' implies a primary use case, but there is no explicit when-to-use vs when-not-to-use guidance, no mention of prerequisites, and no routing to alternative tools for reading the fixture first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Whistle.day - Tournament organizer toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources