Skip to main content
Glama
Sign In
stashcat-api-mcp

stashcat-api-mcp

by dclausen01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_events

Delete one or more calendar events by specifying their event IDs, helping you remove unwanted or outdated schedule entries.

Instructions

Deletes one or more calendar 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_ids": "<event_ids>"
    },
    "name": "delete_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idsYesEvent IDs to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states the action 'deletes' without disclosing side effects such as irreversibility, impact on event invites, permissions required, or whether deletion is permanent. For a destructive operation, this is minimal disclosure.

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 description is a single, clear sentence that is front-loaded with the core action and resource. It is appropriately concise for a simple tool, though it could include more behavioral context without becoming verbose.

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?

The tool is simple (one parameter, no output schema), and the description covers the core purpose and resource. However, lacking annotations, it does not address safety or side effects of deletion, making it only partially complete for safe agent invocation.

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?

The schema covers the single parameter 'event_ids' with a clear description ('Event IDs to delete'), yielding 100% coverage. The description's 'one or more' aligns with the array type but does not add additional meaning beyond the schema. Baseline 3 is appropriate since the schema already documents the parameter.

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 a specific verb 'deletes' and identifies the resource 'calendar events', which clearly distinguishes it from sibling delete tools for other entities (e.g., delete_message, delete_channel). It also specifies 'one or more', indicating it handles multiple events, adding functional clarity.

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?

The description implies usage (use to delete calendar events) but does not provide explicit when-to-use guidance or mention alternatives. It does not state exclusions or contexts where other tools might be more appropriate, leaving usage implied rather than explicitly guided.

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