Skip to main content
Glama

mapumi Wunschzettel und Einladung

Undo a reservation

release_wish
Idempotent

Undo your own reservation. Needs the share link and the reservation_token from reserve_wish.

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": {
      "share_link": "<share_link>",
      "wish_id": "<wish_id>",
      "reservation_token": "<reservation_token>"
    },
    "name": "release_wish"
  }
}

Input Schema

NameRequiredDescriptionDefault
wish_idYesWish id from get_wishlist.
share_linkYesThe share link (https://wunschzettel.mapumi.de/z/…) or just its id.
reservation_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive operation, so the safety profile is covered. The description adds real value by disclosing that only your own reservation can be undone and by tracing where the reservation_token comes from, but it says nothing about what happens to the freed slot or failure modes.

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, front-loaded with the action and immediately followed by the required inputs. Nothing is redundant or padded.

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 3-parameter mutation with annotations present and no output schema, the prerequisite chain is explained well enough to call it correctly. Only minor gaps remain: post-release effects and error behavior are unstated.

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 67%; the schema already explains wish_id and share_link formats. The description compensates for the undocumented reservation_token by stating it comes from reserve_wish, which the schema does not say, and reinforces that the share link is required.

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?

"Undo your own reservation" states a specific verb (undo) and resource (reservation), and the ownership qualifier narrows scope. It does not explicitly distinguish itself from siblings like remove_wish, so an agent must infer the difference, but the action itself 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?

The description implies when to use it (to cancel a reservation you made) and gives prerequisites, namely the share link and the token obtained from reserve_wish. It offers no explicit when-not or comparison to alternatives such as remove_wish, leaving the selection 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