Skip to main content
Glama

check_in_event_attendee

Mark an event attendee registration as present or absent for a specific event session.

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>",
      "sessionId": "<sessionId>",
      "registrationId": "<registrationId>"
    },
    "name": "check_in_event_attendee"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoOptional note or reason
statusNoAttendance status (default: present)
eventIdYesEvent ID
sessionIdYesEvent session ID
registrationIdYesEvent registration ID

Output Schema

NameRequiredDescriptionDefault
dataYesTool result payload — shape varies per tool, see the tool description
summaryYesOne-line human-readable summary of the action
renderTypeYesUI rendering hint for the result

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 readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the description is not the sole safety signal. However, idempotentHint=false is the single most important trait for a check-in tool (does re-checking in create a second record or overwrite the prior status?), and the description is silent on that and on whether a marking can be reversed. It adds the present/absent semantics and the fact that marking is session-scoped, which is genuine value.

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 and no redundancy. It is short to the point of leaving room for the behavioral detail that is missing, but nothing in it is wasted.

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?

The existence of an output schema excuses it from explaining return values, and the schema fully documents all five parameters. But for a non-idempotent mutation with five parameters, the definition does not cover repeat-call behavior or state transitions, which leaves a meaningful gap for an agent deciding whether it is safe to retry.

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 coverage is 100% with per-parameter descriptions and an enum for status, so the schema carries parameter semantics. The description reinforces the status vocabulary ('present or absent') and the session scoping, but adds nothing about the optional reason field or the status default, so it stays at the baseline.

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 ('Mark ... as present or absent') and resource ('event attendee registration'), scoped to 'a specific event session'. This is unambiguous about what the call does, though it does not distinguish itself from any sibling or state what it is not.

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 preconditions (e.g., the registration must already exist and be confirmed), and no mention of alternatives or cases where this should not be called. The agent must infer both the trigger and the prerequisites from the name alone.

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.