Skip to main content
Glama
Sign In

EXZA Remote

by de.exza.remote
OverviewDiscussionsAdmin

Write clipboard text

exza_write_clipboard_text
Destructive

Replace the computer clipboard with provided text, losing its previous content. Do not use to inspect clipboard text; exza_read_clipboard_text is separate. Requires account-bound computer:write OAuth and any prompted local owner approval.

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

Input Schema

NameRequiredDescriptionDefault
textYesUser-approved text to type, append, replace, or report; may be sensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds useful context by warning that previous content is lost and by stating the OAuth scope and possible local owner approval. It does not restate the non-idempotent hint, but the important operational constraints are covered.

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 three tight sentences with the destructive effect front-loaded, followed by the alternative-tool warning and the permission requirement. There is no redundant or filler wording.

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

Completeness5/5

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

For a one-parameter write tool with annotations and no output schema, the description covers purpose, destructive behavior, alternative tool, and authorization requirements. An agent has enough information to call it correctly without opening additional documentation.

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 single text parameter is already documented in the schema, including the sensitive-content caveat. The description adds no parameter-specific syntax or constraints beyond what the schema provides, making the baseline score 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 states a specific verb and resource: 'Replace the computer clipboard with provided text.' It also explicitly distinguishes itself from the sibling read tool by naming exza_read_clipboard_text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when-not-to-use rule: 'Do not use to inspect clipboard text; exza_read_clipboard_text is separate.' This directly routes the agent to the correct alternative for reading.

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

All EXZA Remote toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources