Skip to main content
Glama
bituq

zendriver-mcp

by bituq
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

clear_input

Clears input or contenteditable elements using native setters that controlled components recognize, solving compatibility with React, Vue, and Angular state management.

Instructions

Clear an input or contenteditable element via the native setter.

    Uses the same technique React's synthetic-event system expects so
    controlled components actually see the change. Previously we called
    ``document.execCommand`` which is deprecated and invisible to
    React/Vue/Angular state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4/5.0
Behavior4/5

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

With no annotations, the description carries full burden and explains the technique (native setter) and its advantage over the deprecated execCommand, disclosing the behavioral rationale. However, it does not mention potential side effects or limitations.

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?

The description is two sentences with no extraneous information. The purpose is front-loaded, and the technical context is added efficiently.

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?

Given the simplicity of the tool (one parameter, no output schema), the description covers the why and technical approach. However, the missing explanation of the parameter makes it incomplete for effective use.

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

Parameters2/5

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

Schema description coverage is 0%, but the description does not explain the single required parameter 'selector'. The agent must infer its meaning from the tool name and context, which is insufficient for a parameter with no schema description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool clears an input or contenteditable element via the native setter, distinguishing it from sibling tools like clear_proxy, clear_logs, or clear_storage which operate on different resources.

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?

The description explains when to use this tool (for clearing inputs in a way compatible with React/Vue/Angular state) and why the old execCommand approach is deprecated, providing context but not explicitly stating when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bituq/zendriver-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server