Skip to main content
Glama
Sign In

ZenMaid MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Create appointment in ZenMaid

zenmaid_create_appointment
Read-onlyIdempotent

Create appointment in the user's own ZenMaid account from ChatGPT, Claude or any AI agent. Returns how to do it in ZenMaid step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's ZenMaid Cloud Browser. ZenMaid's official API: ZenMaid has no public API: its help center says it does not support any kind of public API, including REST endpoints, webhooks or programmatic data access (checked 11 Oct 2026).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the description supplies the non-obvious reason: the tool 'opens nothing by itself' and merely returns instructions, which resolves the apparent tension between the 'create' name and a read-only hint. It also explains why browser automation is required (no public API, no REST or webhooks). It does not cover browser session/auth requirements or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the 'opens nothing by itself' caveat are front-loaded, which is good. But the API disclaimer is verbose and self-repeating ('ZenMaid's official API: ZenMaid has no public API...'), and the dated aside adds bulk without helping the agent act.

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 tool with no output schema, the definition covers what is returned (step-by-step screens, buttons, fields) and how to act on it (browser tools). What is missing is a pointer to the alternative zenmaid_* siblings that would be relevant when the task is to reschedule or assign rather than create.

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 schema has zero parameters, so the baseline of 4 applies; there is no parameter meaning for the description to add. The description does not need to explain inputs and correctly focuses on the return content instead.

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 states a specific verb and resource (create appointment in the user's ZenMaid account) and immediately clarifies the deliverable: a step-by-step guide covering screens, buttons and fields. It distinguishes itself from the cotlet_browser_* tools it hands off to. It does not differentiate from cotlet_app_guide, which could plausibly serve a similar guidance role.

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?

It implies the workflow clearly ('then do it with the cotlet_browser_* tools in the user's ZenMaid Cloud Browser'), so an agent knows what follows this call. However it gives no explicit when-not guidance and never routes between this and the zenmaid_reschedule_appointment or cotlet_app_guide siblings, leaving the selection to inference from the tool name.

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

All ZenMaid MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources