Skip to main content
Glama
Sign In

Whistle.day - Tournament organizer

by day.whistle
OverviewDiscussionsAdmin

list_pools

Read-onlyIdempotent

List pools in a stage

Input Schema

NameRequiredDescriptionDefault
stage_idYesStage ID

Output Schema

NameRequiredDescriptionDefault
poolsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "pools": {
+      "items": {
+        "properties": {
+          "advance_count": {
+            "description": "How many entries go through from this pool",
+            "type": "integer"
+          },
+          "id": {
+            "description": "Record ID",
+            "type": "string"
+          },
+          "kind": {
+            "description": "group, winners, losers, final or consolation",
+            "type": "string"
+          },
+          "name": {
+            "description": "Name",
+            "type": "string"
+          },
+          "position": {
+            "description": "Order, 0-based; in a table, the rank",
+            "type": "integer"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "kind",
+          "position",
+          "advance_count"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "pools"
+  ],
+  "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: -[
-  "stage_id",
-  "session_token"
-]New value: +[
+  "stage_id"
+]
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world behavior, so the safety profile is fully covered structurally. The description adds nothing on top of them — no ordering, pagination, empty-result behavior, or note about what a pool contains. It only restates the schema's stage scoping.

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?

Five words, front-loaded with the verb and resource, no filler or hedging. It is appropriately sized for a trivial single-parameter list tool, though it is terse enough that it could afford one clarifying clause without becoming bloated.

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?

An output schema exists, so return values need no explanation, and the annotations cover safety and idempotency. What remains missing is any usage context — for a tool whose resource ('pool') is not otherwise defined anywhere in the description, the definition is barely adequate.

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 description coverage is 100% and the single parameter is documented as 'Stage ID' in the schema, so the description's 'in a stage' phrase is redundant rather than additive. Baseline 3 applies when the schema carries the parameter burden.

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?

Names a specific verb ('List') and resource ('pools') with a scoping qualifier ('in a stage'), so the agent knows exactly what is returned and how it is constrained. It does not need to distinguish itself from siblings since no other pool-named tool exists, but it also gives no hint about what a pool is relative to the closely named list_standings/list_stages family.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives, no preconditions, and no exclusions. The scope 'in a stage' weakly implies the caller must already have a stage, but the requirement is left entirely to the schema.

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