Skip to main content
Glama
Joy MCP Server

Joy MCP Server

Official

joy_open

Open a Joy page in your signed-in Cloud Browser to manage wedding guests, RSVPs, schedules, registry gifts, and messages. Provide a URL to access the page, defaulting to withjoy.com.

Instructions

Open a Joy page in your signed-in Cloud Browser (default https://withjoy.com) to work with wedding guests, RSVPs, schedules, registry gifts and messages.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://withjoy.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses that the browser is already signed in (so no auth step is needed) and gives the default URL. It does not say whether this navigates the current page or opens a new one, what happens on an invalid URL, or whether prior session state is lost.

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 front-loaded sentence that states the action, the environment, the default target, and the content domain. The trailing enumeration of wedding content areas is slightly padded but still serves to scope what the page is used for.

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 single optional-parameter navigation tool with no output schema and no annotations, the definition covers purpose, environment and default adequately. It leaves navigation semantics (same page vs new tab, return value, failure behavior) unstated, which is the main remaining gap.

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 100% and the single optional url parameter is fully documented in the schema, so the baseline is 3. The description merely restates the same default URL already given in the schema, adding no new format or constraint detail.

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?

Specific verb plus resource: 'Open a Joy page in your signed-in Cloud Browser', with the default target domain named. The verb 'open' cleanly separates it from siblings like joy_click, joy_read, joy_type and joy_close, though it never names those siblings explicitly.

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?

The phrase 'to work with wedding guests, RSVPs, schedules...' implies this is the entry/navigation step before reading or clicking, but there is no explicit when-to-use or when-not-to-use guidance, and no stated relationship to joy_read or joy_click.

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