Skip to main content
Glama
Sign In
chromaphore-mcp

chromaphore-mcp

Official
by nodriver-project
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Type

type

Enters text at a human pace, clicking an element by id first, with occasional corrected mistakes and an exact mode for passwords, numbers, and codes.

Instructions

Types text at a human pace (about 6 characters a second), clicking into the element first when an id is given. Rare typos are made and corrected at once, as a person would, except in fields where a wrong character matters (passwords, numbers, codes, card fields); exact: true turns them off.

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

Input Schema

NameRequiredDescriptionDefault
idNoAn element id from a listing, such as a12.
textYes
clearNoSelect what the field holds first, so the text replaces it.
exactNoNo typos at all.
submitNoPress Enter after.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full load and does disclose meaningful traits: typing speed, deliberate typos with immediate correction, exclusion of sensitive fields, and the exact flag. It leaves open what happens with a missing/invalid id, whether it blocks until finished, and whether it requires the page to be focused — significant gaps for a page interaction tool.

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 dense sentence that front-loads the core behavior (human-paced typing) before the exception clause, with zero filler. The long parenthetical enumeration of sensitive field types is slightly heavy but earns its place by defining the exception boundary.

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

Completeness4/5

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

For a five-parameter, no-output-schema interaction tool with no annotations, the description covers the behaviors that drive correct invocation and the key decision point (exact). It could say more about failure modes and whether typing waits for completion, but nothing essential to calling it is missing.

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

Parameters4/5

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

Schema coverage is 80%, so the baseline is 3; the description goes beyond it by explaining that id triggers a click-into-element, that exact disables typo simulation, and that typo suppression is automatic in sensitive fields. clear and submit are left to the schema.

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?

States a specific verb and resource ('Types text') plus the distinctive mechanic (human pace, ~6 chars/sec, clicks into the element when an id is given). This differentiates it cleanly from paste, fill_date and press without needing the schema.

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?

Implies when to prefer it (human-paced input, element targeting handled via id) and names a condition for turning off typo simulation. It does not explicitly compare against paste or fill_date, so the agent must infer the alternative case for bulk/exact insertion.

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