chromaphore-mcp

Official

Overview Schema Source Related Servers Discussions Admin

Paste

paste

Pastes text into a page element using the browser's own clipboard after clicking by element id, so long text is entered as a real paste without touching the machine clipboard.

Instructions

Pastes text with Ctrl+V from the browser's own clipboard (the machine's clipboard is never touched), clicking into the element first when an id is given. Faster than type for long text; the page sees a real paste.

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": "paste"
  }
}

Input Schema

Name	Required	Description	Default
`id`	No	An element id from a listing, such as a12.
`text`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the Ctrl+V mechanism, that the browser's own clipboard is used and the machine clipboard is never touched, and that it clicks into the element first when an id is given. It stops short of describing failure behavior or whether an element must be focusable.

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 dense sentences, no filler; the mechanism and clipboard safety come first, followed by the selection rationale, so the most decision-relevant facts are front-loaded.

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 two-parameter, no-output-schema tool with zero annotations, the description covers mechanism, safety side effects, and targeting behavior adequately. Minor gaps remain around error conditions and return values, but nothing essential for correct invocation 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 only 50% and the 'text' parameter is undocumented in the schema, but the description clarifies it is the text being pasted. It also adds real meaning for 'id': an element is clicked into first, implying that without an id the paste targets whatever is currently focused.

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 ('Pastes text with Ctrl+V') plus the mechanism and clipboard source, which is enough to distinguish it from the sibling 'type' without opening either 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?

Gives a clear selection rule against the obvious alternative ('Faster than type for long text'), but offers no when-not guidance or exclusions (e.g., when type or fill is still preferable, or clipboard-dependent limitations).

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

Deploy Server