Skip to main content
Glama

mapumi Wunschzettel und Einladung

Change list details

update_wishlist
Idempotent

Change child name, occasion, date or the message to gift givers. Only given fields change. 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": "update_wishlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate of the occasion as YYYY-MM-DD (optional).
messageNoOptional message from the parents to everyone giving gifts, shown above the wishes. Line breaks are kept. Empty string removes it.
occasionNoFree text, any culture or religion, e.g. "Geburtstag", "Weihnachten", "Eid al-Fitr", "Diwali".
edit_linkYesThe secret edit link (https://wunschzettel.mapumi.de/b/…) or just its key.
child_nameNoFirst name of the child (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 a non-destructive, idempotent write, so the safety profile is covered. The description adds two genuinely useful behaviors beyond that: only supplied fields are mutated, and a secret edit link is required for authorization. It says nothing about what happens with an invalid/expired edit link or what the response contains.

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 editable fields, followed by the mutation semantic and the auth requirement. No filler or redundancy.

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 five-parameter idempotent mutation with full schema coverage and annotations, the description covers the essentials: what can change, that it is a partial update, and the required credential. The only residual gap is failure/return behavior, which is more forgivable given annotations but still unaddressed with no output schema present.

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%, so all five parameters are documented in the schema, including the message-removal behavior via empty string. The description only restates which fields are editable and that edit_link is required, adding no format or constraint detail beyond the schema — the baseline 3.

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?

States a specific verb (change) and enumerates the exact list-level fields affected: child name, occasion, date, message. This implicitly separates it from the sibling update_wish, which edits individual wishes rather than list metadata, though the description never names that sibling explicitly.

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?

Provides a prerequisite ("Needs the edit link") and clarifies partial-update semantics ("Only given fields change"), which tells the agent it can send a subset of fields. However, it never states when to use this versus update_wish or create_wishlist, nor any conditions under which the call should be avoided.

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