Skip to main content
Glama

Wedding Seat

by com.wedding-seat

Create a wedding project

create_wedding_project

Create a new anonymous Wedding Seat project (no login). Returns a projectKey (your secret handle for all later calls) plus the workspace URL the couple opens in a browser. The projectKey is the ONLY way to access the project again — keep it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoReception date, ISO 8601 (YYYY-MM-DD)
namesNoCouple's names, e.g. 'Ana & Marko' — becomes the project title
localeNoUI language code (e.g. en, sr, de); defaults to en
cultureNoCulture-pack key from list_culture_packs; omit to auto-pick

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description covers key traits: anonymity, return values (projectKey and workspace URL), and the projectKey as the sole access method. It lacks details on errors or rate limits but is adequate for a creation tool.

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 concise sentences with no fluff, front-loading the essential purpose and outcome.

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?

Given no output schema and moderate complexity, the description adequately explains the return values and the importance of the projectKey, though it omits error handling details.

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%, and the description adds no additional parameter information beyond what the schema already provides, meeting the baseline.

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?

The description clearly states the tool creates an anonymous Wedding Seat project, uses specific verbs and resources, and distinguishes itself from sibling tools like add_guests and generate_seating.

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?

The description implies usage context (no login, project creation) and notes the critical importance of the projectKey, but does not explicitly mention when not to use or alternatives.

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

All Wedding Seat toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct action: adding guests, creating project, generating seating, getting summary, listing culture packs, or listing tools. No overlap in purpose.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., add_guests, create_wedding_project, list_tools). No deviations.

Tool Count5/5

6 tools is well-scoped for a wedding planning assistant, covering core operations without being excessive or insufficient.

Completeness4/5

Covers main workflow (create project, add guests, generate seating, view summary) but lacks update/delete for guests or manual seating adjustments. Minor gaps.

Resources