Nyna — AI wedding planner

Turn pasted text into a structured guest list

parse_guest_list

Read-only

[Sign-in required] Parses a pasted guest list — one per line or comma-separated, with or without emails and phones — into structured guests with detected roles — costs no credits (rate-limited to 10 a minute) and returns them for review; add_guests is the separate call that saves the ones kept.

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": {
      "text": "<text>"
    },
    "name": "parse_guest_list"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes	the pasted list, up to 6000 characters
`language`	No

Output Schema

Name	Required	Description
`count`	No
`links`	Yes	pages the user can open
`saved`	No
`guests`	No
`changed`	Yes	whether anything was written
`charged`	Yes	credits actually spent; 0 today for every tool
`summary`	Yes	one human sentence about the result

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations: states sign-in is required, that it costs no credits, that it is rate-limited to 10 per minute, and that it returns results for review rather than persisting. These are exactly the operational facts an agent needs and none are in the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense but front-loaded sentence that leads with the auth requirement and core action; every clause carries information (format, cost, rate limit, sibling routing). Slightly heavy to parse but wastes nothing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists so return values need no explanation, and the description still covers the practical essentials: auth, cost, rate limit, input formats, and persistence boundary. Nothing needed to call it correctly is missing.

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 coverage is only 50% (the 'language' param is undocumented on both sides), but the description compensates for the key 'text' param by specifying accepted formats — one per line or comma-separated, with or without emails/phones — which the schema does not say. The undocumented 'language' param keeps it below a 5.

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 ('parses') and resource ('pasted guest list') plus the output (structured guests with detected roles), and explicitly contrasts with the sibling add_guests. An agent can tell this apart from add_guests 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?

Clearly frames this as a review step that does not save ('returns them for review') and names add_guests as the separate save call, implying the parse-then-add workflow. It stops short of an explicit 'use this before add_guests when the input is pasted text' trigger, but the routing is clear.

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

All Nyna — AI wedding planner 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.