Skip to main content
Glama

zenoti_status

Verify your Cotlet.dev account, available credits, and Zenoti connection are ready before running integration tasks.

Instructions

Check that your Cotlet.dev account and Zenoti are ready: account, credits and Zenoti 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": "zenoti_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 provided, so the description carries the full behavioral burden. It usefully identifies the three areas being checked and the verb 'Check' implies a read-only operation, but it does not disclose permissions, side effects, rate limits, or what happens when a check fails.

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

Conciseness5/5

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

The description is a single front-loaded sentence with a compact colon list. Each listed item (account, credits, Zenoti connection) adds scope, and there is no unnecessary wording.

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 zero-parameter diagnostic tool, the description is adequate to identify what is checked. However, without an output schema, it does not explain the result shape or what 'ready' means, which limits an agent's ability to interpret the response.

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?

There are zero input parameters, so there is no parameter meaning for the description to add. The empty schema already makes the calling contract clear, and the baseline for a parameterless tool is 4.

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: checking Cotlet.dev account and Zenoti readiness. It also enumerates the checked areas (account, credits, Zenoti connection). It does not explicitly differentiate itself from the action-oriented sibling tools, so it falls just short of a 5.

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 readiness-check framing implies a preflight or diagnostic use, but the description never states when to call it, such as before zenoti_open or zenoti_click. No alternatives or exclusions are named, so usage is implied rather than explicit.

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