Skip to main content
Glama

ForeverVow

Create a wedding invite draft

create_invite
Read-only

Make a free Indian wedding invite on ForeverVow with the couple's names and functions (haldi, mehendi, sangeet, wedding, reception…). Returns a link that opens the finished draft in the ForeverVow editor, where the couple can change anything, add photos, an RSVP page and a song, then publish one link to share on WhatsApp and download a free MP4 video and PDF. Ask for any missing names, dates, times or venues first; nothing is published until the couple presses Publish.

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": {
      "bride": "<bride>",
      "groom": "<groom>"
    },
    "name": "create_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
brideYes
groomYes
placeNoCity, e.g. "Jaipur, Rajasthan".
designNoDesign key from list_designs, e.g. "palace", "raj-haveli". Defaults to "palace".
functionsNoEach function in order. Times are local (India) time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Adds real behavioral context: the call only produces an editable draft, returns a link into the ForeverVow editor, and nothing is published until the couple presses Publish. That materially clarifies the effect of a create call in a way annotations alone do not, though there is slight tension with readOnlyHint=true since a draft record is created server-side.

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

Conciseness3/5

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

The front-loaded first sentence is well-structured, but the second sentence is a long run-on that spends many words on downstream marketing features (RSVP page, song, WhatsApp link, MP4, PDF) that are only marginally relevant to invoking this call correctly.

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?

With no output schema, the description usefully explains what comes back (an editor link to the draft). For a five-parameter creation tool with no annotations covering inputs, it covers the essential flow, though it could say more about design validation or function ordering behavior.

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 description coverage is 60%, and the description reinforces the intent of bride/groom and the functions list (with named examples like haldi, mehendi, sangeet) but adds no format, ordering or defaulting detail beyond what the schema already states. The optional place and design parameters are not elaborated on at all.

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 (make/create a wedding invite draft), names the product surface (ForeverVow editor) and the concrete inputs it needs (couple's names and functions). An agent can tell this apart from list_designs or get_invitation_messages without opening the schemas.

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 a clear precondition to gather missing names, dates, times and venues before calling, and implies design keys come from list_designs (reinforced in the schema). It does not explicitly name a when-not or point to a sibling for the browse-only cases, so it stops just short of full routing guidance.

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