Skip to main content
Glama

mapumi Wunschzettel und Einladung

Change party details

update_party
Idempotent

Change name, age, date, times, place, address, notes or wish list link. Only given fields change. Needs the party 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_party"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoAge the child turns (optional).
dateNoParty day as YYYY-MM-DD, today up to one year ahead.
notesNoNotes for the parents of the guests, e.g. pickup time, what to bring (optional).
placeNoWhere, shown to all guests, e.g. "bei uns zu Hause" (optional).
addressNoFull address, shown to a guest only after they said yes (optional).
end_timeNoEnd as HH:MM (optional).
edit_linkYesThe secret party edit link (https://www.mapumi.de/einladung/e/…) or just its key.
child_nameNoFirst name of the birthday child.
start_timeNoStart as HH:MM (optional).
wishlist_linkNoShare link of the child's wish list (https://wunschzettel.mapumi.de/z/…), optional. Empty string removes it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true). The description adds two facts those hints do not convey: the update is partial (only supplied fields change, so untouched data is preserved) and a secret edit link is required for authorization. It stops short of describing failure modes for an invalid or expired edit link.

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, no filler: the changeable set first, then the partial-update rule, then the prerequisite. Everything an agent needs is front-loaded and nothing repeats the title verbatim.

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 10-parameter mutation tool with full schema coverage and no output schema, the description covers purpose, partial-update semantics, and the auth token requirement. Minor gaps remain around what a successful response confirms and how an invalid edit link fails, but nothing blocks correct invocation.

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 the schema already explains every parameter, including format constraints and the empty-string removal behavior for wishlist_link. The description's field list largely restates the schema property names without adding syntax, defaults, or interaction rules, so it sits at the baseline.

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?

The description opens with a specific verb ('Change') and enumerates the resources affected (name, age, date, times, place, address, notes, wish list link), so an agent knows exactly what is mutated. It does not name or differentiate against siblings like update_wish or update_wishlist, which is the only thing keeping it from a 5.

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?

'Only given fields change' tells the agent this is a partial update, so unlisted fields are safe, and 'Needs the party edit link' states the prerequisite for the call. There is no explicit when-not-to-use or pointer to an alternative sibling, but the context for choosing it is clear.

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