Skip to main content
Glama

Admit tournament entrants

admit_event_entrants
Destructive

A tournament organizer accepts entrant requests for the listed player ids from get_my_event. 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": "admit_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?

The annotations already declare this is a non-readonly, open-world, destructive operation. The description adds the required authorization scope, which is helpful beyond annotations, but it does not explain what state change or destructive effect occurs when requests are admitted.

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?

It is a short, front-loaded sentence with no filler. The action is stated first, followed by the identifier source and authorization requirement.

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?

For a destructive, open-world tournament mutation with five parameters and no output schema, the description is too thin. It omits what eventToken identifies, how token should be supplied, and what accepting requests does to pending entrant state.

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?

With only 40% schema description coverage, the description needs to compensate for undocumented parameters. It usefully says userIds come from get_my_event, but it says nothing about token or eventToken, leaving key inputs unexplained.

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 gives a specific action: a tournament organizer accepts entrant requests for listed player ids. The phrase 'entrant requests' distinguishes it reasonably from a plain add-entrant operation, though it does not explicitly name or contrast with siblings such as add_event_entrants.

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 provides a useful prerequisite ('Requires mcp:manage') and tells the agent where the player ids come from ('from get_my_event'). However, it gives no explicit when-not guidance and does not distinguish this from adding entrants directly or other entrant-management siblings.

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