Skip to main content
Glama

Delete Event

delete_event
Destructive

Delete an event. Requires confirm set to DELETE.

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": {
      "eventId": "<eventId>"
    },
    "name": "delete_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicit confirmation for this write. Pass the exact literal this tool requires (for example DELETE) only after the user approves the action.
eventIdYesEvent ID, from a Nas.com product listing for this business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / confirm / description
      Added value: +"Explicit confirmation for this write. Pass the exact literal this tool requires (for example DELETE) only after the user approves the action."
    • addedInput schema / properties / eventId / description
      Added value: +"Event ID, from a Nas.com product listing for this business."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is known. The description adds the confirmation guardrail, which is real behavioral context, but says nothing about irreversibility, side effects on related data, or permissions; the confirm literal is also already documented in the schema.

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 short sentences with no filler, and the operation is front-loaded ahead of the precondition. Every word earns its place.

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?

For a two-parameter destructive tool the definition covers the essentials: what it does and the confirmation gate. It omits whether deletion is permanent, what happens to dependent records, and what is returned on success, which leaves meaningful gaps for a destructive operation despite the annotations.

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 both eventId and confirm are already documented, including the example literal DELETE. The description restates the confirm requirement but adds no new meaning such as format, source, or validation rules beyond the schema, so the baseline 3 applies.

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 gives a specific verb and resource ("Delete an event") that an agent can immediately distinguish from create_event, update_event, get_event, and publish_event. It does not explicitly name or contrast a sibling, but the operation 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 verb plus the stated precondition that confirm must be set to DELETE, which tells the agent this is a two-step guarded action. There is no explicit guidance on when to prefer deletion versus unpublish_event or other alternatives, so routing is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources