Skip to main content
Glama

mapumi Wunschzettel und Einladung

Reserve a wish

reserve_wish

For relatives: mark a wish as "I'll give this" so nobody else buys it. Returns a reservation_token; keep it to undo with release_wish. Needs the share 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": {
      "share_link": "<share_link>",
      "wish_id": "<wish_id>"
    },
    "name": "reserve_wish"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional name of who gets the gift, e.g. "Oma Rosi". Shown to parents and family.
wish_idYesWish id from get_wishlist.
share_linkYesThe share link (https://wunschzettel.mapumi.de/z/…) or just its id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 but non-destructive, non-idempotent write. The description adds genuinely useful context beyond them: the call returns a reservation_token that must be stored to undo later. It is silent on what happens if the wish is already reserved by someone else or whether the reservation expires, which are the main behavioral risks.

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, each doing distinct work: purpose, return-and-undo contract, and input requirement. The purpose 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?

With no output schema present, the description compensates by describing the returned reservation_token and its role. Conflict handling and token lifetime are the only notable omissions for a three-parameter mutation.

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 all three parameters are already documented, including the optional gift-recipient name. The description only restates that the share link is required, adding no syntax or format detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ("mark a wish as 'I'll give this'") plus the audience ("For relatives") and the intent ("so nobody else buys it"). It also names release_wish as the inverse operation, so an agent can place it against siblings without opening schemas.

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?

Gives a clear condition for use (relatives reserving a gift before others buy it) and explicitly routes the undo case to release_wish. It does not cover exclusions such as when to use update_wish instead for editing a wish, so it stops short of full when/when-not coverage.

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