Charlotte

charlotte_type

Type text into a specified input element by ID, with options to clear existing text, type character-by-character for autocomplete, and press Enter. Returns the updated page content for verification.

Instructions

Type text into an input element. Returns full page representation after typing.

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_id": "<element_id>",
      "text": "<text>"
    },
    "name": "charlotte_type"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	Text to enter
`slowly`	No	Type one character at a time with a delay between keystrokes. Use for sites with autocomplete, search-as-you-type, or per-key validation (default: false)
`element_id`	Yes	Target input element ID
`clear_first`	No	Clear existing value before typing (default: true)
`press_enter`	No	Press Enter after typing (default: false)
`character_delay`	No	Milliseconds between keystrokes (implies slowly: true). Default when slowly is true: 50ms. Total typing time is capped at approximately 30s (including per-keystroke overhead); requests whose estimated duration exceeds that are rejected.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.8.0Aug 10, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / character_delay / description

Previous value: -"Milliseconds between keystrokes (implies slowly: true). Default when slowly is true: 50ms"New value: +"Milliseconds between keystrokes (implies slowly: true). Default when slowly is true: 50ms. Total typing time is capped at approximately 30s (including per-keystroke overhead); requests whose estimated duration exceeds that are rejected."

removedInput schema / properties / press_enter / $ref
```
Removed value: -"#/properties/clear_first"
```
addedInput schema / properties / press_enter / type
```
Added value: +"boolean"
```
removedInput schema / properties / slowly / $ref
```
Removed value: -"#/properties/clear_first"
```
addedInput schema / properties / slowly / type
```
Added value: +"boolean"
```

First observedv0.6.3May 26, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It states the return type (full page representation) but does not disclose that typing may clear existing content by default, can trigger events, or requires the element to be visible/interactable. The default clearing behavior (clear_first: true) is only discoverable through the schema, not the description.

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 concise sentences with no wasted words. It front-loads the primary purpose and adds a useful behavioral note about the return representation, fitting the appropriate structure for a simple tool.

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?

Despite having 6 parameters and no output schema or annotations, the description is minimal but sufficient to understand the core action. The schema covers parameter semantics, and the description states the return type. However, it lacks context about default behaviors (e.g., clearing the field, pressing Enter) that would help an agent anticipate side effects, making it adequate but not comprehensive.

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%, so the baseline is 3. The description itself does not add meaning beyond the schema, but the schema parameters are well-documented with descriptions for each field. Since the description does not need to repeat schema details, a score of 3 is appropriate.

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 a specific verb ('Type') and resource ('input element'), and explicitly notes it returns the full page representation after typing. This distinguishes it from sibling tools like charlotte_click, charlotte_select, and charlotte_submit, which perform different actions.

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 description implies the tool should be used when text needs to be entered into an input element, but it does not explicitly discuss when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. No guidance is given for distinguishing between typing and using charlotte_submit or charlotte_click for form interactions.

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