Skip to main content
Glama

cleanmanager_type

Enter text into a specified numbered field on the active CleanManager page to complete forms or update records using the field number from the last read.

Instructions

Type text into a numbered field on the current CleanManager page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>",
      "text": "<text>"
    },
    "name": "cleanmanager_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to type.
elementYesField number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does not say whether typing replaces or appends to existing field content, whether it submits the form, what happens on an invalid field number, or whether the page must be focused first — meaningful gaps for a text-entry action.

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 sentence with no filler, and the target ('numbered field on the current CleanManager page') is front-loaded rather than buried. Its brevity is genuine conciseness rather than padding.

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 simple two-parameter tool with full schema coverage and no output schema, the description covers the core action adequately. It is still incomplete about prerequisites and overwrite semantics, which matter because the tool acts on live page state.

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 coverage is 100%, so both parameters are already documented in the schema, establishing a baseline of 3. The description adds only that the field is 'numbered' and on the 'current' page, which corroborates but does not extend the schema's own explanation.

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 ('Type text') and a specific target ('a numbered field on the current CleanManager page'), which separates it from cleanmanager_read and cleanmanager_click. It stops short of naming a sibling or explicitly contrasting behavior, so it lands at clear-but-undifferentiated.

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 phrase 'on the current CleanManager page' implies prerequisites (a page must already be open), and the schema note 'Field number from the last read' implies a prior cleanmanager_read. However, the description itself never states when to use this versus cleanmanager_click or what to do when no read has happened.

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