Skip to main content
Glama

ForeverVow

Wedding invitation messages for WhatsApp

get_invitation_messages
Read-only

Ready-to-send wedding invitation messages for WhatsApp in English, Hindi and Hinglish (formal, warm, for friends, reminder). Replace the sample names, date and city with the couple's.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_invitation_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context that the returned content is a template containing sample names, date and city that must be substituted. It stops short of saying how many messages are returned or in what structure, which matters for a zero-parameter tool that presumably returns everything at once.

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?

A single front-loaded sentence with no filler, and the actionable substitution instruction is placed at the end where it is easy to catch. The parenthetical 'formal, warm, for friends, reminder' is slightly compressed and leaves it ambiguous whether these are four distinct tone variants.

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

Completeness3/5

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

For a simple read-only content tool with no output schema, the description covers what the content is and how to use it. It leaves open whether a single message or a set across languages and tones is returned, which is the main thing an agent needs to plan its next step.

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?

The tool takes zero parameters, so the baseline of 4 applies. The description correctly implies the caller cannot select a language or tone at invocation time, though it does not state outright that all variants are returned together.

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?

The description names the concrete resource (ready-to-send wedding invitation messages for WhatsApp) and its variants by language and tone, so an agent knows exactly what comes back. It does not explicitly contrast with siblings like create_invite, but the retrieval-vs-creation distinction is clear from the wording.

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?

Usage is only implied: 'Replace the sample names, date and city with the couple's' tells the agent this is a template source to be adapted downstream, which suggests when to reach for it. There is no explicit when-to-use vs when-not guidance and no mention of create_invite as the alternative for actually sending an invite.

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