Skip to main content
Glama

Respond to invitation

respond_to_event

Accept, tentatively accept, or decline a meeting invitation and optionally send a note to the organizer.

Instructions

Accept, tentatively accept or decline a meeting invitation, optionally with a message to the organizer.

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": {
      "id": "<id>",
      "response": "<response>"
    },
    "name": "respond_to_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEvent ID (or the meeting request message ID)
sendNoSend the response to the organizer (default true)
messageNoNote to the organizer
responseYes

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 readOnlyHint=false, destructiveHint=false and openWorldHint=true, covering the safety profile. The description adds that a note can be sent to the organizer, but it does not explain the effect of send=false, whether the calendar entry is updated locally, or that the organizer is notified externally.

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?

One front-loaded sentence with the action alternatives first and the optional message qualifier second. No filler and no repetition of the title.

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 four-parameter mutation with no output schema, the description covers what changes but omits the side effects an agent would want to know: whether the organizer is emailed when send defaults true and whether the local event status is updated. Adequate but with identifiable gaps.

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 75%, so the schema does most of the work; the only undescribed parameter is the response enum, whose values the description restates. It clarifies that the message is a note to the organizer, but adds nothing about id or the send flag beyond the schema.

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 three specific verbs (accept, tentatively accept, decline) against a specific resource (meeting invitation), so an agent knows exactly what action is performed. It does not explicitly contrast itself with update_event, but the response semantics are distinctive enough to be unambiguous.

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 is implied rather than stated: it applies to invitations the user has received, which the description conveys through 'meeting invitation'. There is no explicit guidance on when to prefer this over update_event or on any preconditions (e.g. invitation must be pending).

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