Skip to main content
Glama
Treatwell MCP Server

Treatwell MCP Server

treatwell_status

Verify your Cotlet.dev account, credits, and Treatwell connection are ready before using the Treatwell MCP Server.

Instructions

Check that your Cotlet.dev account and Treatwell are ready: account, credits and Treatwell 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": "treatwell_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/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. It does disclose the three things inspected (account, credits, connection), which tells the agent this is a low-risk introspection call, but it says nothing about whether the call touches the network, what happens on a failed check, or whether any state is mutated.

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 the verb first and the three checked items listed compactly. Nothing is wasted, though the unexplained 'Cotlet.dev' reference and the trailing colon list are slightly abrupt.

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, no-output-schema readiness check, the description covers what is inspected but not what the result looks like or how a partial failure (e.g. credits low, connection down) should be interpreted. Adequate but leaves the agent guessing at the return semantics.

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 the baseline is 4 and there is no parameter meaning the description could add. The enumerated check items are contextual rather than schema-replacing.

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?

States a specific verb ('Check') and enumerates the three resources inspected: account, credits, and Treatwell connection. This is distinguishable from the sibling browser-interaction tools (click/open/read/type), though the description never explicitly frames itself as the non-interactive readiness check.

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?

'Check that ... are ready' implies a pre-flight verification step before using the other treatwell_* tools, but the guidance is only implied. There is no explicit 'call this before X', no when-not-to-use, and no mention of what to do if a check fails.

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