Skip to main content
Glama

Respond to Meeting Invitation

respond_to_event
Destructive

Accept, decline, or tentatively accept a meeting invitation, optionally include a comment, and choose whether to notify the organizer or update only your calendar.

Instructions

Accept, decline or tentatively accept a meeting invitation. By default the organizer gets the response by email, with the comment if one is given.

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

Input Schema

NameRequiredDescriptionDefault
commentNoNote to include in the response
event_idYesThe event ID of the invitation
responseYesHow to respond
send_responseNoSend the response to the organizer (default: true). False updates only your calendar.

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 declare readOnlyHint=false and destructiveHint=true, and the description usefully explains the real side effect: a response email is sent to the organizer by default, carrying the comment. That is genuine added context. However, it does not say whether an existing response can be overwritten or how to respond without notifying the organizer beyond the schema's send_response 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?

Two short sentences with no wasted wording, and the primary action is front-loaded ahead of the side-effect note. The email behavior sentence earns its place as the key consequence an agent should know about.

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 tool with full schema coverage and no output schema, the description covers the essential behavior, including the notification side effect and the role of the comment. Minor omissions are the handling of already-responded invitations and required permissions.

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 are already documented, including send_response's default of true and the enum for response. The description's note about the comment being included and the default email behavior largely restates what the schema already states, so it adds little beyond 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?

States a specific verb set (accept/decline/tentative) against a specific resource (meeting invitation), which is clearly distinct from update_event or delete_event. It stops short of naming any sibling explicitly, so sibling differentiation is implied by the action 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 Guidelines3/5

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

Usage is implied by the phrase "meeting invitation" -- you call this when you have received one and need to reply. There is no explicit guidance on when to use update_event or delete_event instead, and no mention of preconditions such as whether the invitation must still be pending.

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

Deploy Server

Other Tools