Skip to main content
Glama

check_in_event_ticket

Check in an attendee using the event ID and the ticket code supplied at admission.

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": {
      "eventId": "<eventId>",
      "code": "<code>"
    },
    "name": "check_in_event_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
eventIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already disclose the safety profile (not read-only, not idempotent, not destructive), so the description's job is to add detail on what actually happens. It does not say what occurs on an invalid or already-used code, whether a repeat call double-checks-in the attendee, or what state changes on the ticket, leaving nearly all behavioral burden on the annotations.

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?

A single front-loaded sentence with no filler or repetition. It is tight, though arguably too terse given the gaps in guidance elsewhere.

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 state-changing, non-idempotent operation with two undocumented parameters and no output schema. For that complexity, the agent needs at minimum what happens on failure and whether re-invocation is safe, neither of which is present.

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 0%, so the description must compensate. It does identify both parameters in plain language and clarifies that "code" is the ticket code presented at admission rather than an arbitrary identifier, which adds real meaning. However, it says nothing about the UUID format, scoping to the event, or validation behavior.

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 ("Check in an attendee") with the two inputs that identify the record. The verb distinguishes it from the destructive sibling void_event_ticket, but the definition never explicitly contrasts the two, so differentiation is inferential 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisite or exclusion conditions (already checked in, voided ticket, wrong event), and no mention of alternatives such as void_event_ticket. The phrase "supplied at admission" hints at the context but gives the agent no decision rule.

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