Skip to main content
Glama

Add players to a tournament

add_event_entrants

A tournament organizer adds the selected Praetorium players by id. Confirm the player names and tournament before calling. 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": {
      "token": "<token>",
      "userIds": "<userIds>"
    },
    "name": "add_event_entrants"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
userIdsYes
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.
eventTokenNo
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare it as a non-read-only, non-destructive, open-world operation, so the description is not responsible for the basic safety profile. It adds genuinely useful context — the mcp:manage scope requirement and the instruction to confirm names and tournament before mutating — but says nothing about duplicate handling, whether entrants are appended or replaced, or consequences of a wrong id.

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?

Three short sentences, front-loaded with the action and followed by the caution and the auth requirement. No filler, though the second and third sentences could be merged without loss.

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?

For a five-parameter mutation tool with no output schema, the definition covers purpose, auth scope, and a safety prompt, which is a reasonable baseline. It falls short on parameter meaning and on how the tournament is identified, which the agent must guess from the schema alone.

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 coverage is only 40%, so the description needs to compensate and largely does not. 'By id' gestures at userIds, but the required 'token' and the optional 'eventToken' (presumably the tournament reference) are never explained, and the analytics-only params go unmentioned in either direction.

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 states a concrete verb and resource ('adds the selected Praetorium players by id' to a tournament) plus the actor (organizer), so an agent knows the intent. It does not differentiate this from the similarly named 'admit_event_entrants' sibling, and 'Praetorium' is domain jargon that may not be self-explanatory.

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?

It gives the actor framing (organizer) and a confirmation step ('Confirm the player names and tournament before calling'), which implies when it is appropriate. It says nothing about when NOT to use it or how it differs from admission, check-in, or invite siblings, leaving selection between roster-mutation tools to inference.

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