Aisle

Remove Wedding Event

remove_my_event

DestructiveIdempotent

Removes an identified event from the selected wedding and returns the removed event's id and name. Requires sign-in and an Aisle membership.

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

Input Schema

Name	Required	Description	Default
`event_id`	Yes	Identifier of the event to remove from the selected wedding.
`wedding_id`	No	Identifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 12, 2026

addedInput schema / properties / event_id / format
```
Added value: +"uuid"
```

addedInput schema / properties / event_id / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

First observedOct 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is largely covered. The description adds genuinely useful context beyond that: the authentication/membership requirement and the fact that the removed event's id and name are returned.

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?

Two tightly written sentences with zero filler; the core action is front-loaded and the return value plus prerequisite follow. Nothing is wasted.

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 simple destructive mutation with no output schema, the description covers purpose, required auth, and the return payload, while annotations cover irreversibility. It stops short of noting side effects such as cascading changes to related guests or places.

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%, with event_id and wedding_id both documented in the schema, so the schema carries the semantic load. The description only loosely touches the 'selected wedding' scoping and adds no format or multi-wedding nuance 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 pairs a specific verb ('Removes') with a clear resource ('event from the selected wedding') and even states the post-condition (returns the removed event's id and name). It is easy to distinguish from remove_my_guest or remove_my_place by resource, though it never explicitly contrasts with siblings.

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 only implied: removing an identified event. The description states a precondition ('Requires sign-in and an Aisle membership') but offers no when-to-use routing, no exclusions, and no pointer to alternatives like update_my_event or remove_my_accommodation.

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

All Aisle tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?