Skip to main content
Glama

mapumi Wunschzettel und Einladung

Add guests

add_guests

Invite more children. Each gets their own guest_link. 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>",
      "guests": "<guests>"
    },
    "name": "add_guests"
  }
}

Input Schema

NameRequiredDescriptionDefault
guestsYesFirst names of the invited children.
edit_linkYesThe secret party edit link (https://www.mapumi.de/einladung/e/…) or just its key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent behavior. The description adds value beyond that by disclosing the side effect (a unique guest_link generated per child) and the authorization requirement (secret edit link), which explains why the operation is not idempotent.

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 action, then the effect, then the prerequisite. Nothing is redundant and no sentence could be dropped without losing information.

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 two-parameter mutation with full schema coverage and clear annotations, the definition covers purpose, side effect, and prerequisite adequately. The only minor gap is that guest_link is introduced but there is no output schema explaining what the call returns.

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 both parameters are already fully documented, including the edit-link URL format and name constraints. The description only reiterates that edit_link is required and that guests are children, adding no new semantics beyond the schema.

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?

"Invite more children" names a specific verb and resource, and the note about each receiving its own guest_link makes the operation's effect concrete. It implicitly contrasts with remove_guest by saying "more", but never names a sibling, so it stops short of full differentiation.

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?

"Needs the party edit link" gives a real prerequisite for invocation, which is useful context an agent must know before calling. However, there is no statement of when to use this versus remove_guest or create_party, nor any exclusion (e.g., that the party must already exist).

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