Skip to main content
Glama
Joy MCP Server

Joy MCP Server

Official

joy_guide

Guides users through Joy's wedding planning screens for guests, RSVPs, schedules, registry gifts, and messages, and gives the sign-in link needed to get started.

Instructions

How to work in Joy (wedding guests, RSVPs, schedules, registry gifts and messages): its screens and the sign-in link. Call this first.

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": "joy_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Joy, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the scope of guidance and that a sign-in link is included, but it does not state whether the tool is read-only and non-mutating, nor what the guide's response looks like (prose, steps, links).

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?

Two compact clauses with the domain scope front-loaded and the imperative ('Call this first') placed last for emphasis. No filler, though the parenthetical list of domains is dense.

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 one-optional-parameter guidance tool with no output schema, the description should clarify whether the response is static orientation or shaped by the 'task' input, and that it performs no actions. Those gaps are real but modest given the tool's simplicity.

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?

The single 'task' parameter is fully documented in the schema ('What you want done in Joy, in your words'), so coverage is 100% and the schema does the work. The description adds nothing about how the task string influences the guidance returned, so baseline 3 applies.

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 resource (Joy's screens and sign-in link) and scopes it with concrete domains: wedding guests, RSVPs, schedules, registry gifts and messages. It is clear this is an orientation/help tool rather than an action tool, though it never explicitly contrasts itself with the joy_open/joy_read/joy_click siblings.

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?

'Call this first' gives an explicit ordering cue that tells the agent when to reach for this tool relative to the other Joy tools. There is no explicit when-not guidance or named alternative, which keeps it short of a 5.

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