Skip to main content
Glama

mapumi Wunschzettel und Einladung

Remove a wish

remove_wish
DestructiveIdempotent

Remove one wish from the list. 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>",
      "wish_id": "<wish_id>"
    },
    "name": "remove_wish"
  }
}

Input Schema

NameRequiredDescriptionDefault
wish_idYesWish id from get_wishlist.
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

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the deletion semantics are covered structurally. The description contributes the authorization requirement (the secret edit link is needed to act), but does not say whether removal is permanent or recoverable, nor what happens to a reserved wish.

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?

Two short sentences, front-loaded with the action and followed by the requirement; nothing is padded. The second sentence slightly duplicates the schema's required edit_link, keeping it just short of ideal.

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, fully documented, annotated tool this is close to adequate, but it leaves open whether a removal is irreversible and how it differs from releasing a wish. Those are the questions an agent must resolve before invoking a destructive operation.

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 both wish_id and edit_link documented in the schema. The description's mention of the edit link merely echoes the schema and adds no format, validation, or fallback detail beyond it, so the baseline of 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?

"Remove one wish from the list" gives a specific verb (remove) and bounded resource scope (one wish), which is clearer than the title alone. It does not, however, distinguish itself from siblings like release_wish, which an agent could plausibly confuse with removing a wish.

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 states a prerequisite ("Needs the edit link"), which is real usage context, but it offers no when-to-use versus when-not guidance relative to release_wish or update_wish. The prerequisite is also already enforced by the schema's required fields, so it adds little routing value.

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