Skip to main content
Glama
Sign In
duplex

duplex

by Eric-huang799
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

type

Enter text into input, textarea, or contenteditable fields using a reference or CSS selector, optionally pressing Enter to submit.

Instructions

Type text into an input/textarea/contenteditable, by ref or CSS selector. Optionally press Enter after.

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": {
      "target": "<target>",
      "text": "<text>"
    },
    "name": "type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
clearNoClear existing value first (default true)
tabIdNo
submitNoPress Enter after typing
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

C2.9/5.0
Behavior2/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 notes the optional Enter press, but omits whether typing requires prior focus, how it handles a missing/unmatched target, whether it waits for the element, and what happens to existing text by default (clear=true is only in the 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 compact sentences with the core action front-loaded and the optional Enter behavior appended. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter mutation tool with no annotations and no output schema, the description leaves significant gaps: focus/waiting requirements, error behavior on unmatched selectors, and the semantics of clear/tabId are unaddressed.

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 only 40% (text and target lack descriptions), so the description must compensate. It usefully clarifies that 'target' accepts either a ref or a CSS selector and that submit triggers Enter, but it says nothing about the 'clear' default behavior or 'tabId' scoping.

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) and the exact targets it accepts (input/textarea/contenteditable), which clearly separates it from siblings like click, press, or hover. It does not explicitly name which sibling to use for adjacent needs (e.g., press for Enter alone), so it stops short of 5.

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?

The description says what it does but never states when to choose it over siblings such as press or evaluate, nor any prerequisites (e.g., element must exist or be focused first). An agent must infer the selection context from the tool name alone.

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

Deploy Server

Other Tools