Skip to main content
Glama

cleanmanager_guide

Explains how to use CleanManager: find screens, sign-in link, and complete tasks for schedules, check-ins, customers, quality reports, and storage. Call this first before other CleanManager actions.

Instructions

How to work in CleanManager (manage cleaning schedules, check-ins, customers, quality reports and storage): its screens and the sign-in link. Call this first.

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_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in CleanManager, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/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 implies a safe, read-only orientation call and tells the agent what topics are covered, but says nothing about what is actually returned (text guide? screen list? link?) or whether the guide is static versus adapted to the supplied task. That is a meaningful gap for a tool with no output schema.

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?

Two sentences, zero filler, with the scope of coverage front-loaded and the imperative usage rule last. Nothing could be removed without losing information.

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 single-optional-parameter reference tool with no output schema, the description covers purpose, scope, and call ordering adequately. The main missing piece is a hint about the shape of the returned guidance, which matters because no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single optional 'task' parameter with 100% schema description coverage, so the schema already explains it as 'what you want done, in your words.' The description adds no further meaning, such as how the task string shapes the guidance or what happens when it is omitted. Baseline 3 applies given the complete schema coverage.

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 names a specific resource (CleanManager documentation) and enumerates the domains it covers — schedules, check-ins, customers, quality reports, storage — plus screens and the sign-in link. It is clearly a guidance/onboarding tool rather than a UI action, which separates it in spirit from the click/open/type siblings, although it never names them explicitly.

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?

"Call this first" gives a concrete ordering rule an agent can act on before attempting the sibling UI tools. It lacks any explicit when-not-to-use condition (e.g., skip it if you already know the screen layout), so it falls short of a full 5.

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