Skip to main content
Glama
Joy MCP Server

Joy MCP Server

Official

joy_click

Clicks a numbered element on the current Joy page to interact with wedding planning data such as guests, RSVPs, schedules, or gifts.

Instructions

Click a numbered element on the current Joy page.

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": {
      "element": "<element>"
    },
    "name": "joy_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely does not meet it. It does not say what happens after the click (navigation, page change, DOM mutation), whether the page state is destroyed, or how a stale element number is handled.

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 short, front-loaded sentence with no filler. It could be marginally sharper by noting the prerequisite read, but nothing is wasted.

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-parameter tool with full schema coverage and no output schema, the essentials are present. The remaining gap is consequence disclosure — what a click does to page state and expected failure modes — which matters because no annotations cover it.

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 parameter is already documented as 'Element number from the last read.' The description reinforces the tie to the current page and a prior read, but adds no syntax or format meaning beyond the schema.

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?

A specific verb (click) and resource (a numbered element on the current Joy page), which is enough to distinguish it from siblings like joy_type or joy_status. It stops short of explicitly naming a sibling or stating how it differs from joy_type on an input-like element.

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 'numbered element ... from the last read' implies the tool must be preceded by a read/guide call, which is useful implicit sequencing. However, there is no explicit when-not guidance or stated alternative for entering text into a field instead of clicking it.

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