Skip to main content
Glama

Approve or decline a tournament entrant

moderate_event_entrant
Destructive

A tournament organizer accepts or rejects one entrant by id 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>",
      "userId": "<userId>",
      "status": "<status>"
    },
    "name": "moderate_event_entrant"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
statusYes
userIdYes
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

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the description does not need to restate that this is a destructive write. It does add useful context by naming the required scope (mcp:manage), but it says nothing about side effects such as whether the entrant is notified, whether rejection is reversible, or whether the decision can be changed later.

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?

Two short sentences with the action front-loaded and the permission requirement trailing. Nothing is redundant and no sentence could be removed without losing information.

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 destructive six-parameter mutation with no output schema, the description covers the essential what and the permission gate, but omits outcome information: what the response contains, what happens to a rejected entrant, and what the optional eventToken does. An agent could call it correctly but not predict the result.

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?

With only 33% schema coverage, the description partially compensates: it clarifies that the entrant is identified by an id obtained from get_my_event, and 'accepts or rejects' maps onto the status enum. It leaves eventToken, llm_model and conversation_id completely unexplained, so two of the six parameters carry no meaning anywhere.

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 pair (accepts or rejects) and a specific resource and scope (one entrant), and points to get_my_event as the id source, which separates it from bulk tools like add_event_entrants and admit_event_entrants. It stops short of explicitly distinguishing itself from the closest moderation sibling, so a 4 rather than a 5.

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 tournament organizer' plus 'by id from get_my_event', and the mcp:manage prerequisite is stated. However, there is no explicit when-not guidance, no mention of check_in_tournament_entrant or admit_event_entrants as alternatives, and no note about the state an entrant must be in to be moderated.

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