Ringske

Add guest

add-guest

Adds an invitation to the guest list, e.g. "Andrea & Michael" (counted as 2 unless a size is given). Invited to the given moments, or to every moment that guests can see when none are given. Use update-guest afterwards to write down an answer.

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": {
      "name": "<name>"
    },
    "name": "add-guest"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	As on the envelope: "Andrea & Michael", "Familie Peeters".
`size`	No	How many people the invitation covers, children included.
`email`	No	For the invitation and RSVP mails.
`notes`	No	Private notes of the couple.
`category`	No	Guest category name; created when it does not exist yet.
`children`	No	How many of those are children.
`invited_by`	No	Whose guest: partner_a, partner_b or both (default).
`moment_ids`	No	Moments to invite them to (see list-moments). Default: every moment visible to guests.
`dietary_notes`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare this is a non-destructive, closed-world write, so the safety bar is met. The description adds real behavioral rules the annotations don't carry: the default party size of 2 and the fallback invitation to every guest-visible moment. It omits notable side effects such as whether supplying an email triggers invitation mail, which keeps it from a 5.

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, with the core action and its default behaviors front-loaded before the follow-up routing to update-guest. Every sentence 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?

For a 9-parameter mutation tool with no output schema and rich schema descriptions, the definition covers the key defaults and the natural next step. It leaves a small gap around return values and mail side effects, but an agent could still call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is high (89%), so the baseline would be 3. The description still adds interpretive meaning by explaining that an invitation without an explicit size counts as 2, which clarifies why size is optional and how it interacts with the name format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Adds an invitation to the guest list") and immediately clarifies the default counting semantics. It also distinguishes itself from update-guest by framing that tool as the follow-up for recording an RSVP answer, so an agent can tell the two apart without opening either schema.

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?

Gives clear when-to-use context: create the invitation now, then call update-guest afterwards to record the answer. It also explains the default invitation scope (all guest-visible moments when none are given). It stops short of explicit exclusions or prerequisites, such as when to prefer an existing guest record over creating one.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Ringske tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?