Skip to main content
Glama

Squadcard

Set up the game

set_game
Destructive

Set when and where a squad plays (organisers only). Players can then say if they're in. This replaces the whole game: anything left out goes back to its default (no venue, no cost, no player limit), so pass what should stay; get_squad shows the current game. If the next kick-off stays the same, answers and picked teams are kept; if it moves, everyone answers again and the squad is told.

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": {
      "squadId": "<squadId>",
      "startsLocal": "<startsLocal>"
    },
    "name": "set_game"
  }
}

Input Schema

NameRequiredDescriptionDefault
venueNoWhere you play.
repeatNoDefault weekly. custom = every repeatWeeks weeks.
squadIdYesThe squad's id, from list_squads.
pitchCostNoThe pitch's cost, split between who plays. Tracking only: Squadcard never moves money.
playerLimitNoAnyone after this many goes on a waitlist.
repeatWeeksNoWith repeat custom: the weeks between games.
startsLocalYesThe next kick-off in the squad's own time zone: YYYY-MM-DDTHH:mm.
durationMinutesNoLength in minutes. Default 60.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / durationMinutes / description
      Previous value: -"Default 60."New value: +"Length in minutes. Default 60."
    • removedInput schema / properties / durationMinutes / enum
      Removed value: -[
      -  60,
      -  90,
      -  120
      -]
    • addedInput schema / properties / durationMinutes / maximum
      Added value: +300
    • addedInput schema / properties / durationMinutes / minimum
      Added value: +15
    • changedInput schema / properties / repeat / description
      Previous value: -"Default weekly."New value: +"Default weekly. custom = every repeatWeeks weeks."
    • changedInput schema / properties / repeat / enum
      Previous value: -[
      -  "weekly",
      -  "fortnightly",
      -  "none"
      -]New value: +[
      +  "weekly",
      +  "fortnightly",
      +  "none",
      +  "custom"
      +]
    • addedInput schema / properties / repeatWeeks
      Added value: +{
      +  "description": "With repeat custom: the weeks between games.",
      +  "maximum": 52,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint: true), the description provides crucial behavioral context on state management, explaining that parameters not passed return to defaults, and that date shifts trigger re-interaction with players.

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?

The definition is dense due to the complexity of the state logic it describes. However, the structure is logical, moving from high-level purpose to specific mutation rules and user impact without excessive fluff.

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?

Given the high complexity (8 parameters and mutable state), the description is highly complete. It addresses the 'what happens next' regarding player interaction, which is vital for proper tool usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While the schema coverage is perfect (100%), the description adds critical functional semantics, specifically detailing how the 'replace' mechanism works and how the date change impacts the player response state.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The purpose is stated clearly: 'Set when and where a squad plays'. It is clearly distinguished from sibling tools by its function as a comprehensive game parameter configuration tool for organizers.

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?

It provides explicit scope constraints ('organisers only') and defines the expected workflow by referencing `get_squad`, allowing the agent to know when this tool should be the source of truth for state.

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.