Skip to main content
Glama
Sign In
chromaphore-mcp

chromaphore-mcp

Official
by nodriver-project
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Press keys

press

Sends a keyboard key or chord, such as Enter, Tab, Ctrl+A, or F5, to the Chromaphore browser, enabling navigation, shortcuts, and form control.

Instructions

Presses a key or a chord: Enter, Escape, Tab, ArrowDown, Ctrl+A, Shift+Tab, F5.

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": {
      "keys": "<keys>"
    },
    "name": "press"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysYes
timesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 and falls short. It does not say whether presses are repeated automatically, whether a target element must be focused first, what happens on an unrecognized key, or whether modifier state is held between calls. Only the chord syntax itself conveys real behavioral information.

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 compact sentence, front-loaded with the action, followed by a useful enumeration. The list is a little dense but every example earns its place by clarifying accepted key names.

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 keyboard-input tool with no annotations, no output schema, and undocumented parameters, the definition should cover repeat semantics, focus/preconditions, and error behavior. None of these appear, leaving meaningful gaps for correct invocation.

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% for two parameters. The examples partially document the keys format, but the times parameter (integer, 1-20) is never mentioned, so its repeat behavior and constraints are invisible to the agent. One of the two parameters is effectively undocumented.

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?

The description states a specific verb (presses) and resource (a key or a chord), and the enumerated examples like "Ctrl+A" and "Shift+Tab" make the accepted input grammar concrete. It stops short of distinguishing the tool from siblings such as type or click, but the intent is still unambiguous.

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?

There is no statement of when to use this instead of type, click, or fill_date, and no note about focus requirements. Usage is only implied by the keyboard examples. An agent must infer that typing text belongs to type while single keys and hotkey chords belong here.

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