Skip to main content
Glama

mapumi Wunschzettel und Einladung

Delete party

delete_party
DestructiveIdempotent

Delete the invitation and all answers for good. Guest links stop working. Ask the user before calling. Needs the party edit link.

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": {
      "edit_link": "<edit_link>"
    },
    "name": "delete_party"
  }
}

Input Schema

NameRequiredDescriptionDefault
edit_linkYesThe secret party edit link (https://www.mapumi.de/einladung/e/…) or just its key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, but the description adds important context: deletion is permanent ('for good'), it cascades to all answers, guest links break, and the caller must confirm with the user first. This goes well beyond what the annotations cover and states the real consequence of the operation.

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?

Four short sentences, each carrying distinct information: the effect, the cascade, the confirmation rule, and the prerequisite. The destructive consequence is front-loaded and there is no filler.

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 single-parameter destructive tool with rich annotations and no output schema, the definition covers scope, permanence, confirmation, and the credential. The only gap is what is returned on success, which is minor because the annotations already describe the safety profile.

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

Parameters4/5

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

Schema coverage is 100% and the schema explains the edit_link format, so the input is already well documented. The description adds that the link functions as a required credential rather than just an identifier, which is the one piece of meaning the schema does not convey.

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 (delete) with the concrete scope of what is erased: the invitation and all answers. It also clarifies that 'party' means the invitation, which removes ambiguity from the tool name and separates it from delete_wishlist, a different resource.

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?

It gives an explicit pre-call rule ('Ask the user before calling') and a prerequisite ('Needs the party edit link'). There is no named alternative or when-not-to-use branch, but the close siblings operate on different resources, so the guidance covers the practical decision point.

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