Skip to main content
Glama

rsvp_event

Join or cancel the authenticated user's participation in a Zindies event. Requires a Bearer token (User API token).

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": {
      "event_id": "<event_id>"
    },
    "name": "rsvp_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNojoin (default) to participate, cancel to leave.join
localeNoResponse language for translatable text fields (names, titles, descriptions). Pass the language the user is conversing in when it is one of the supported locales. Fields without a translation fall back to their source language. Default: ja.
commentNoOptional comment to attach when joining (ignored for cancel).
event_idYesNumeric ID of the event.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world mutation, so the safety profile is covered. The description adds genuine value with the authentication requirement (User API token, not an app token), which annotations do not convey. It does not disclose the effects of cancel (whether an attached comment is discarded, whether capacity/attendee lists change) or whether repeated joins error out, which matters given idempotentHint=false.

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, zero filler: the action scope comes first and the auth constraint second. Nothing here is redundant with the title or restates the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter mutation with full schema coverage and clear annotations, the description supplies the one non-schema item an agent truly needs before calling: the token type. Return behavior needs no explanation since there is no output schema to describe. The remaining gap is minor — no mention of what happens to an attached comment on cancel or of failure modes.

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 100%, so all four parameters (action, locale, comment, event_id) are already documented with enums and defaults, making 3 the baseline. The description adds no parameter-level meaning beyond that, such as the interaction between comment and cancel or whether locale affects only response text versus stored state.

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 and resource: 'Join or cancel the authenticated user's participation in a Zindies event.' That is far more informative than the bare name rsvp_event and makes clear this is the mutation tool for event participation, not a read like get_event. It stops short of explicitly contrasting itself with any sibling, but no sibling appears to share this behavior.

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?

The only usage guidance is a prerequisite: a Bearer token (User API token) is required. There is no statement of when to prefer this over get_event or list_events, nor any when-not guidance (e.g., cannot RSVP to a past or full event). The join/cancel choice is left entirely to the schema's enum description.

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