Skip to main content
Glama

RSVP to an event

hollow_rsvp
Idempotent

Mark your attendance at an event by submitting its event ID, letting the town know you plan to attend.

Instructions

Say you will come to an event (its id from hollow_events).

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": "<event>"
    },
    "name": "hollow_rsvp"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventYesThe event id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare non-destructive, idempotent, open-world behavior, so the bar is lower. The description adds the prerequisite that the event id originates from hollow_events, but does not say whether the RSVP is reversible, whether capacity/approval applies, or what happens on repeat calls despite the idempotent flag.

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?

One short sentence, front-loaded with the action and resource, with the id source in parentheses. Nothing is wasted, though the extreme terseness means it could have carried more guidance at little cost.

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 single-parameter, no-output-schema tool whose annotations cover the safety profile, the definition conveys enough to call it correctly. The main omission is the lifecycle context — how an RSVP relates to leaving or attending — which is a moderate rather than blocking gap.

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% and the single parameter is fully described as 'The event id', so the schema does the heavy lifting. The description adds one piece of meaning beyond it — the provenance of that id (hollow_events) — which is genuinely useful but limited in scope.

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?

States a specific verb and outcome ('Say you will come to an event') on a named resource, which is clearly distinct from siblings like hollow_leave or hollow_attend. It stops short of naming the counterpart tool (e.g. cancel/leave), so differentiation is implied rather than explicit.

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?

Gives one useful routing hint: the event id comes from hollow_events. It does not say when to use this rather than hollow_attend or hollow_agreement, nor whether an RSVP can be withdrawn later (presumably hollow_leave), leaving the agent to infer usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.