stashcat-api-mcp

respond_to_event

Set your response to a calendar invitation by accepting, declining, or resetting to open using event and user IDs.

Instructions

Respond to a calendar event invitation (accept, decline, or reset to open).

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

Input Schema

Name	Required	Description
`status`	Yes	Response status
`user_id`	Yes	Your own user ID
`event_id`	Yes	Event ID to respond to

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description carries the full transparency burden. It discloses the available statuses, including the ability to reset to 'open', which implies reversibility. However, it does not mention permissions, side effects (e.g., notifications to organizer), or what happens if the event is past, so it is only partially transparent.

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 sentence, front-loaded with the verb and resource, no filler. Every word contributes meaning.

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?

Given the low complexity (3 params, simple enum, no output schema), the description plus schema covers the core information. However, the absence of annotations and output schema means the description could have been more helpful by noting expectations (e.g., permissions, return value), so it is minimally adequate.

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?

All three parameters are fully described in the schema, giving a high schema_description_coverage, so the baseline is 3. The description does not add any additional parameter semantics beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'Respond' and clearly identifies the resource as 'calendar event invitation', with the three possible statuses. This distinguishes it from sibling tools like 'invite_to_event' and the channel-specific invite tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description makes the use case clear—responding to calendar event invitations—which tells the agent when to use it. It does not explicitly name alternatives or exclusion conditions, such as 'use accept_channel_invite for channel invitations', so it stops short of full explicit guidance.

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

Deploy Server