Skip to main content
Glama

mapumi Wunschzettel und Einladung

Change a wish

update_wish
Idempotent

Change text, link, price, picture (image_url) or favorite of one wish. Only given fields change. A new link fetches picture and price again unless price is given too. 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": "update_wish"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkNoOptional product link. The product picture (and title, if text is empty) is fetched from the page.
textNoThe wish, short and concrete. Optional if a link is given: then the product title is used.
priceNoOptional price as text, e.g. "39,99 €". Filled from the product page when a link is given and price is empty. Empty string removes it.
wish_idYesWish id from get_wishlist.
favoriteNoMark as a top wish (heart).
edit_linkYesThe secret edit link (https://wunschzettel.mapumi.de/b/…) or just its key.
image_urlNoOptional direct URL of the main product picture (https://…jpg/png/webp), e.g. the og:image of the product page if you have seen it. Used when the picture cannot be fetched from the page, many shops block our server. Empty string removes it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / image_url
      Added value: +{
      +  "description": "Optional direct URL of the main product picture (https://…jpg/png/webp), e.g. the og:image of the product page if you have seen it. Used when the picture cannot be fetched from the page, many shops block our server. Empty string removes it.",
      +  "maxLength": 1000,
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the safety profile is largely covered. The description adds one genuinely valuable non-obvious trait: setting a new link re-fetches picture and price unless price is supplied. There is mild tension with openWorldHint=false given the outbound product-page fetching described, though that is not a direct contradiction.

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?

Four short sentences, front-loaded with the scope and the most surprising side effect, with no filler. Slightly telegraphic phrasing ("Needs the edit link") slightly reduces fluency but not information density.

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 7-parameter mutation tool with no output schema, the definition covers field selection, prerequisites, and the fetch side effect well. It leaves unstated what the call returns and how fetch failures surface, which would help an agent recover from errors.

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%, so the baseline is 3, but the description adds meaning beyond the schema by naming the fields that can be changed and stating the condition under which link overrides price and image_url. It still does not clarify how favorite toggling behaves or what a partial-failure looks like.

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?

Opens with a specific verb ("Change") plus a scoped resource ("one wish") and enumerates the mutable fields, so an agent can tell it apart from update_party or update_wishlist at a glance. It stops short of naming those siblings, so the differentiation is implied by scope rather than stated.

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?

"Only given fields change" and "Needs the edit link" give useful patch semantics and a prerequisite, and the link/price interaction rule is spelled out. There is no explicit when-to-use versus when-not guidance and no routing to alternatives such as remove_wish or release_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