Skip to main content
Glama

cleanmanager_status

Check that your Cotlet.dev account, credits, and CleanManager connection are ready before running cleaning workflows.

Instructions

Check that your Cotlet.dev account and CleanManager are ready: account, credits and CleanManager 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": "cleanmanager_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 provided, so the description carries the full behavioral burden. It does disclose the three things inspected (account, credits, CleanManager connection) and the read-only nature is implied by "Check", but it says nothing about the return shape, what a failure looks like, or whether any auth/prerequisite is required before calling.

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 enumerated checks after the colon. The word "account" appears twice (once in the readiness claim, once in the enumeration), which is mild redundancy but also a deliberate mapping of what is verified.

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 with no output schema and no annotations, the description covers what is checked but not what is reported back. Since the entire value of a status tool is its report, the absence of any hint about the result shape leaves a real gap.

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 explain and the baseline is 4. Nothing in the description contradicts the empty schema.

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 gives a specific verb ("Check") and a specific subject: readiness of the Cotlet.dev account, credits, and the CleanManager connection. This clearly separates it from the sibling UI-automation tools (open, read, type, click), which act on a page rather than verifying preconditions. It stops short of explicitly naming a sibling as the contrasting alternative.

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 word "ready" strongly implies this is a preflight/health check to run before the other CleanManager tools, but that sequencing is left to inference. There is no explicit statement of when to call it, when not to, or what to do with a failed result.

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