Skip to main content
Glama
Joy MCP Server

Joy MCP Server

Official

joy_status

Verify that your Cotlet.dev account, credits, and Joy connection are ready before managing wedding planning data.

Instructions

Check that your Cotlet.dev account and Joy are ready: account, credits and Joy connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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. 'Check' plus the enumerated subjects strongly implies a read-only diagnostic, which is useful, but it says nothing about side effects, auth requirements, latency, cost, or whether a failed check blocks subsequent joy_* calls.

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; the purpose and the checked subjects arrive immediately. It is efficient, though the trailing list of three checks is slightly compressed rather than expanded into actionable meaning.

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?

For a zero-parameter diagnostic with no output schema and no annotations, the description is nearly sufficient — it tells the agent what is being verified. The one gap is that it does not indicate what a positive or negative result looks like, which matters since no output schema exists to explain returns.

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 there is nothing to disambiguate and the baseline of 4 applies. The description correctly adds no irrelevant argument discussion.

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 a specific verb ('Check') and enumerates the concrete resources being verified: account, credits, and Joy connection. That distinguishes it from the sibling tools (joy_click, joy_open, joy_read, etc.), which are actions rather than diagnostics, though it never explicitly contrasts itself with them.

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: a readiness check naturally precedes Joy interactions, so an agent can infer 'call before acting.' However, there is no explicit statement of when to call it, how often (once per session vs. before every action), or what to do if the check fails.

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