Skip to main content
Glama
Sign In

ZenMaid MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Get schedule in ZenMaid

zenmaid_get_schedule
Read-onlyIdempotent

Get schedule 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_get_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds meaningful context beyond that: it returns procedural steps (screens, buttons, fields), performs no action itself, and explains why browser automation is required (no public API, no REST/webhooks). That is substantive behavioral disclosure.

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 core behavior and handoff are front-loaded and clear, but the final sentence about ZenMaid's lack of a public API is long and somewhat tangential. It earns partial place by justifying the browser-tool handoff, yet could be trimmed without losing the actionable guidance.

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?

With no output schema, the description carries the burden of explaining returns, and it does so ('how to do it in ZenMaid step by step (screens, buttons, fields)'). Combined with the explicit next-step tooling, an agent has enough to invoke and follow through correctly.

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 no parameter semantics to document and the baseline of 4 applies. The description correctly implies no inputs are needed to retrieve the guide.

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 ('Get schedule in the user's own ZenMaid account') and clarifies the actual output is step-by-step instructions rather than schedule data. This resolves the ambiguity created by the name, though the name/behavior mismatch means an agent must read the description to understand it is a guide tool, not a data fetcher.

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?

It explicitly says the tool 'opens nothing by itself' and directs the agent to follow up with the cotlet_browser_* tools in the Cloud Browser, which is a clear usage path. It does not contrast against siblings like zenmaid_list_customers or cotlet_app_guide, so the routing guidance is good but not exhaustive.

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