Skip to main content
Glama

mapumi Wunschzettel und Einladung

Delete wish list

delete_wishlist
DestructiveIdempotent

Delete the whole list for good, including all reservations. Ask the user before calling. Needs the 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_wishlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
edit_linkYesThe secret edit link (https://wunschzettel.mapumi.de/b/…) or just its key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is known, but the description adds the key blast-radius detail that all reservations are destroyed along with the list and that the action is permanent ('for good'). Authentication is also surfaced via the edit-link requirement. It stops short of saying what the response looks like or whether recovery is possible.

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?

Three short sentences, front-loaded with the effect ('Delete the whole list for good, including all reservations'), followed by the confirmation requirement and the prerequisite. No wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 full annotation coverage and no output schema, the description covers everything needed: what is destroyed, that it is irreversible, that user confirmation is required, and what credential is needed.

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 coverage is 100% and the edit_link property is fully described in the schema, so the description's 'Needs the edit link' adds only the confirmation that it is mandatory. Baseline 3 applies when the schema already carries the parameter meaning.

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 gives a specific verb and resource ('Delete the whole list') and immediately scopes it against wish-level siblings by noting it removes 'all reservations' too. An agent can distinguish this from remove_wish or release_wish without opening the schema.

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 states a clear usage precondition — 'Ask the user before calling' — and a hard prerequisite ('Needs the edit link'), which is stronger than most mutation tools. It does not, however, name any alternative when the user only wants to remove a single wish.

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