Skip to main content
Glama

Create a hidden-list game

create_hidden_list_game

A group organizer starts a game where players seal their lists before the reveal. Use the group’s token and confirm the format and points. Requires mcp:manage.

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": {
      "groupToken": "<groupToken>"
    },
    "name": "create_hidden_list_game"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamsNo
formatNo1v1
roundsNo
scheduleNo
timeZoneNo
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
allowancesNo
allyPointsNo
groupTokenYes
soloPointsNo
rosterLimitNo
pointsBudgetNo
sharedPointsNo
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.
clockLimitMinutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

The annotations already establish that this is a non-read-only, non-destructive, open-world creation call. Beyond them, the description adds two genuinely useful facts: that the lists are sealed until the reveal, which is the defining behavior of this tool, and that a mcp:manage permission is required. That last item is an authentication prerequisite the annotations do not supply.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences and front-loaded with the core purpose, which is good structural discipline. But the brevity comes at the cost of usefulness: with 15 parameters and only 1 required, the space saved by not explaining points, schedule, or allowances is a real gap rather than real concision.

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

Completeness2/5

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

This is a 15-parameter creation tool with a nested schedule object, defaults, enums, and no output schema. The description covers only the token, format, and points at a high level and leaves the agent to infer the meaning of the remaining dozen parameters, including the nested scheduling fields and the boolean sharedPoints. That is not sufficient to call the tool correctly.

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

Parameters2/5

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

Schema description coverage is only 13% across 15 parameters, so the description must compensate, and it does not. It mentions only groupToken, format, and points broadly; teams, rounds, schedule/sealBy/playsAt, timeZone, allowances, allyPoints, soloPoints, rosterLimit, sharedPoints, and clockLimitMinutes receive no explanation of format, units, or effect. The single sentence 'confirm the format and points' does not resolve the distinction between pointsBudget, soloPoints, allyPoints, and sharedPoints.

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 names a specific verb and resource: a group organizer starts a hidden-list game in which players seal their lists before the reveal. That mechanism clearly distinguishes it from create_battle and choose_hidden_list_side without requiring the schema. However, it does not explicitly name which sibling tool to use instead for a non-hidden game or to join an existing game.

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?

Usage context is implied by 'A group organizer starts a game' and made partially explicit by 'Use the group's token and confirm the format and points,' which tells the agent which inputs matter. There is no explicit when-not guidance, no mention of alternatives such as create_battle for a different game type, and no prerequisites beyond the permission note.

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