Skip to main content
Glama
Sign In

Whistle.day - Tournament organizer

by day.whistle
OverviewDiscussionsAdmin

create_handoff

Destructive

Make a link that hands this tournament to a person. They open it, set an email and a password, and the account this session has been acting as becomes theirs. Single use, and it expires. Afterwards this connection can no longer change the tournament — which is the point, so hand it over when the tournament is ready rather than when you are still building it. Only for a tournament made without signing in; a signed-in account already owns what it creates.

Input Schema

NameRequiredDescriptionDefault
tournament_idYesTournament ID

Output Schema

NameRequiredDescriptionDefault
urlYesThe link to give to the person taking the tournament over
noteYesWhat to tell the person, and what changes once they open it
expiresYesWhen the link stops working, UTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "expires": {
+      "description": "When the link stops working, UTC",
+      "type": "string"
+    },
+    "note": {
+      "description": "What to tell the person, and what changes once they open it",
+      "type": "string"
+    },
+    "url": {
+      "description": "The link to give to the person taking the tournament over",
+      "type": "string"
+    }
+  },
+  "required": [
+    "url",
+    "expires",
+    "note"
+  ],
+  "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: -[
-  "tournament_id",
-  "session_token"
-]New value: +[
+  "tournament_id"
+]
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only flag destructive/non-idempotent/closed-world; the description adds the truly consequential behavior: single use, expiry, ownership transfer, and permanent loss of this connection's ability to modify the tournament. It also documents the precondition (unsigned-in tournament) that annotations cannot express.

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?

Front-loaded with the core action and only mildly conversational ('which is the point'). Every sentence carries information, though the aside-about-readiness could be trimmed without loss.

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

Completeness5/5

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

An output schema exists so return values need no explanation, and the description still covers preconditions, irreversibility, expiry, and the post-handoff state. An agent has everything required to decide whether to call it.

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?

The schema covers tournament_id at 100% description coverage, so the parameter is already documented; the description refers to 'this tournament' but adds no format, ID source, or validation detail beyond the schema. Baseline 3 applies when the schema does the heavy lifting for a single param.

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: creates a link that hands a tournament to a person, with the exact mechanic (recipient sets email/password and takes ownership of the current session's account). It is specific enough to separate from siblings like publish_tournament, though it never names an alternative explicitly.

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?

Gives explicit when-to-use ('hand it over when the tournament is ready rather than when you are still building it') and an explicit exclusion ('Only for a tournament made without signing in; a signed-in account already owns what it creates'). Nothing is left to inference.

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