Skip to main content
Glama

mapumi Wunschzettel und Einladung

Remove a guest

remove_guest
DestructiveIdempotent

Take a guest off the list. Their link stops working. 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>",
      "guest_id": "<guest_id>"
    },
    "name": "remove_guest"
  }
}

Input Schema

NameRequiredDescriptionDefault
guest_idYesGuest id from get_party.
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 destructiveHint=true and idempotentHint=true, so the safety profile is known; the description still adds real value by explaining the consequence ("Their link stops working") and the credential required (party edit link). It does not say whether the guest is notified, whether removal is recoverable beyond re-adding, or whether already-answered invitations are affected.

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, each carrying distinct information: action, effect, prerequisite. No filler and the action is front-loaded.

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 annotation coverage and no output schema, this covers action, side effect, and credential, which is close to sufficient. Minor gaps remain around notification side effects and whether the operation can be undone.

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%, with guest_id explicitly sourced from get_party and edit_link documented with an example URL format. The description only restates the edit_link requirement in prose, so it adds no semantics beyond the schema; 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?

A concrete verb-plus-object ("Take a guest off the list") that cannot be confused with the wishlist/wish siblings, which operate on different resources. It stops short of naming a sibling such as add_guests as the inverse operation, so differentiation is implied by the noun rather than stated, but the purpose is unmistakable.

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?

The description states a prerequisite ("Take a guest off the list... required guest_id implies a guest that exists") via " Needs the edit_link", telling the caller what is required to act. However it gives no when-to-use/when-not guidance, no mention of the inverse add_guests, and no warning about when removal is inappropriate.

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