Skip to main content
Glama

graph_respond_to_event

Respond to a meeting invite by accepting, declining, or tentatively accepting it, with an optional comment and control over sending the response to the organizer.

Instructions

RSVP to a meeting invite.

Args: event_id: The event ID to respond to. response: Response type: "accept", "decline", or "tentative". comment: Optional comment to send with the response. send_response: Whether to send the response to the organizer (default true). user: Shared or delegated calendar owner address or user ID to act on. Empty targets your own calendar. Requires the delegated Calendars.Read.Shared or Calendars.ReadWrite.Shared permissions.

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": "graph_respond_to_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNo
commentNo
event_idYes
responseYes
send_responseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: it discloses that send_response defaults to true (i.e., the organizer is notified), names the delegated permission scopes required for acting on another user's calendar, and explains that an empty user targets your own calendar. It does not say whether the response is reversible or how re-responses are handled.

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?

The one-line purpose is front-loaded, followed by a clean Args block where every line corresponds to a parameter and earns its place. The docstring formatting is slightly verbose but not redundant.

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 five-parameter mutation tool with no annotations and no output schema, the description covers parameters, side effects, and auth requirements well. It leaves unstated what the tool returns and what errors arise if the user is not an invitee, which keeps it from a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it does for all five parameters: the event_id target, the three allowed response values, the optional comment, the send_response default and its effect, and the non-obvious 'user' semantics including empty-value behavior and permission requirements. This adds real meaning beyond the bare types and enum.

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 opening line gives a specific verb and resource ('RSVP to a meeting invite'), which is clearly distinct from sibling operations such as graph_update_event, graph_cancel_event, or graph_get_event. It stops short of explicitly naming an alternative, but the action is 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 by the purpose: use it to answer an invite you have received. There is no explicit when/when-not guidance, no mention of prerequisites like fetching the event first via graph_get_event, and no note about what happens if a response was already recorded.

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