Skip to main content
Glama

Whistle.day - Tournament organizer

list_courts

Read-onlyIdempotent

The courts a tournament is played on. Their ids are what update_fixture's court argument takes.

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": {
      "tournament_id": "<tournament_id>"
    },
    "name": "list_courts"
  }
}

Input Schema

NameRequiredDescriptionDefault
tournament_idYesTournament ID

Output Schema

NameRequiredDescriptionDefault
courtsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "courts": {
      +      "items": {
      +        "properties": {
      +          "active": {
      +            "description": "Whether it is in use",
      +            "type": "boolean"
      +          },
      +          "id": {
      +            "description": "Record ID",
      +            "type": "string"
      +          },
      +          "name": {
      +            "description": "Name",
      +            "type": "string"
      +          },
      +          "position": {
      +            "description": "Order, 0-based; in a table, the rank",
      +            "type": "integer"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "name",
      +          "position",
      +          "active"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "courts"
      +  ],
      +  "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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world scope, so the safety profile is covered. The description's added value is the id interlock with update_fixture, but it says nothing about ordering, filtering, or how courts are scoped beyond the tournament.

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?

Two short sentences with no filler, and the resource definition is front-loaded before the id-usage hint. The fragmentary first sentence is telegraphic but efficient.

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?

With an output schema present, the description need not explain return values, and the single required parameter is schema-documented. The only real gap is the absence of an explicit listing verb and any note on result ordering or scope.

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?

Only one parameter exists and schema coverage is 100%, so the schema already documents tournament_id. The description adds no format or constraint detail beyond that, which is the expected baseline when the schema does the work.

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?

The description identifies the resource precisely ('the courts a tournament is played on') and ties it to a concrete downstream consumer, update_fixture's court argument, which separates it from the write-side sibling add_court. It never states the verb 'list', so the agent relies on the tool name for the action, but the resource and scope are unambiguous.

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?

The second sentence gives a clear reason to call this tool: to obtain the court ids that update_fixture expects. That is actionable context for a read-before-write workflow, though no explicit when-not or alternative (e.g. add_court) is named.

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