Skip to main content
Glama

mapumi Wunschzettel und Einladung

Create party invitation

create_party

Create a birthday party invitation with personal links for each guest. Returns edit_link (secret, for parents) and guests with their guest_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": {
      "child_name": "<child_name>",
      "date": "<date>"
    },
    "name": "create_party"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoAge the child turns (optional).
dateYesParty 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).
guestsNoFirst names of the invited children.
addressNoFull address, shown to a guest only after they said yes (optional).
end_timeNoEnd as HH:MM (optional).
child_nameYesFirst 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

B3.4/5.0
Behavior3/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=false), so the bar is lower. The description does add real value by disclosing the return payload (edit_link and guest_link per guest) and flagging that edit_link is a secret for parents, but it never addresses the non-idempotent behavior implied by the annotations, i.e. that repeated calls create additional parties.

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, zero filler, with the resource and the output contract front-loaded. Every clause carries information an agent needs.

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 10 fully documented parameters and no output schema, the description correctly compensates by describing the return values and the edit_link secrecy caveat. What is missing is the mutation semantics (duplicate creation on repeat calls, whether an existing party can be modified instead) that matter for a non-idempotent create tool.

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%, and the schema already documents formats, limits, and optionality for all 10 parameters. The description only loosely links 'personal links for each guest' to the guests array; it adds no format or constraint meaning beyond the schema, so the baseline 3 applies.

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+resource ('Create a birthday party invitation') and adds scope detail ('personal links for each guest'), which clearly distinguishes it from siblings like create_wishlist or add_guests. It stops short of naming an alternative outright, so it is clear but not maximally differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance: nothing says this is the first step before add_guests/answer_invitation, nor when to prefer create_wishlist or update_party. The agent must infer the workflow entirely from the tool name and required parameters.

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