Skip to main content
Glama

cleanmanager_open

Opens a CleanManager page in your signed-in Cloud Browser so you can manage cleaning schedules, check-ins, customers, quality reports, and storage.

Instructions

Open a CleanManager page in your signed-in Cloud Browser (default https://cleanmanager.com) to work with manage cleaning schedules, check-ins, customers, quality reports and storage.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://cleanmanager.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It usefully discloses that the browser is already 'signed-in' (auth context) and supplies a default URL, but omits whether the call navigates an existing tab, launches a session, waits for page load, or returns page content versus just a handle.

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?

One compact sentence with the action and destination front-loaded, which is appropriate for a simple navigation tool. Minor awkwardness in 'to work with manage cleaning schedules' and a feature list that adds bulk without routing value.

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 single-optional-parameter tool with no output schema, the essentials (target and default) are present. However, with zero annotation coverage the description should say more about what the call returns and whether a browser session must pre-exist, which it leaves unstated.

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?

Schema description coverage is 100% and the single optional 'url' parameter is documented in the schema with the same default. The description only repeats that default, adding no format constraints (absolute URL only? relative paths allowed?) beyond what the schema already states, so baseline 3 applies.

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 (Open) and resource (a CleanManager page in a signed-in Cloud Browser), plus the default destination URL. It does not explicitly distinguish itself from the sibling 'cleanmanager_read', which an agent could plausibly confuse with 'open a page to read its content'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use, when-not-to-use, or prerequisite guidance. The phrase about 'work with cleaning schedules, check-ins, customers, quality reports and storage' describes domain coverage rather than selection criteria, and nothing tells the agent whether a session must be started via cleanmanager_status first or when to prefer cleanmanager_read.

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