Skip to main content
Glama

Players join session

gameye_player_join

Register one or more players as joined in a Gameye session and return the session's player count and IDs; use dryRun to preview the request without sending data.

Instructions

Register one or more players as joined in a Gameye session. Returns the session's player count and IDs as reported by the server. Pass dryRun=true to preview the request. Needs GAMEYE_API_TOKEN; without one, returns setup steps and sends nothing.

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": {
      "session": "<session>",
      "players": "<players>"
    },
    "name": "gameye_player_join"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNoReturn the exact request that would be sent, with the API token masked, and send nothing
playersYesOne or more player IDs
sessionYesSession ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, but the description adds real value beyond them: it discloses the returned data (player count and IDs as reported by the server), states that dryRun masks the token and sends nothing, and explains the missing-token fallback (returns setup steps, sends nothing). The one gap is that idempotentHint=false is never interpreted — what happens if a player is already joined is unstated.

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

Conciseness5/5

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

Four short sentences with zero filler, ordered from what the tool does, to what it returns, to the preview option, to the auth prerequisite. Every sentence carries distinct information an agent needs before calling.

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 no output schema, the description compensates by describing the return value, and it covers the mutation's safety profile via annotations plus the auth failure mode. It falls short only on duplicate/repeat-call semantics and error behavior, which matter for a non-idempotent write.

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%, so each of the three parameters is already documented in the schema, including the token-masking dryRun behavior. The description's mentions of 'players', 'session' and dryRun largely restate the schema and add no syntax, format or constraint detail beyond it, so baseline 3 applies.

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 first sentence gives a specific verb and resource: 'Register one or more players as joined in a Gameye session', which clearly distinguishes this from the sibling gameye_player_leave. It never names an alternative tool or states the inverse case explicitly, so differentiation is inferred from the verb rather than stated.

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?

The description implies the use case (marking players as joined in an existing session) and gives one concrete operational guideline: pass dryRun=true to preview. It offers no explicit when-not guidance, no prerequisites around session state (e.g. must the session be running?), and no routing to sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.