Skip to main content
Glama

phone_clipboard

Read or set the Android phone clipboard; if Android 10+ returns empty reads for background apps, access the clipboard while the app is in the foreground.

Instructions

Read the phone clipboard, or set it (set="text"). Android 10+ may hide the clipboard from background apps, so reading can come back empty.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "phone_clipboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
setNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden, and it does disclose a real behavioral caveat: on Android 10+ background apps may get an empty clipboard read, so the agent knows an empty result is not necessarily an error. It leaves other behavior unstated, such as permission requirements or what a set call returns.

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 short sentences, with the primary action and the write-mode toggle front-loaded before the caveat. Nothing is padded or repeated.

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?

The tool is simple: one optional parameter, no annotations, and no output schema, so the description does not need to explain return values. Covering both modes plus the empty-read failure mode is nearly sufficient, though a note on write permissions or the success signal from a set call would close the remaining gap.

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

Parameters5/5

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

The single parameter has 0% schema coverage, so the description must fully define it, and it does: set="text" switches the tool from read to write, and omitting set means read. That is the complete semantics an agent needs for this parameter.

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 names a concrete resource (the phone clipboard) and both operations, read (default) and write (via set="text"). No sibling tool touches the clipboard, so an agent can distinguish this tool from phone_type or phone_screen without opening 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 Guidelines3/5

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

It implies the two usage modes clearly: call with no arguments to read, pass set to write. However, there is no guidance on when to prefer this tool over alternatives such as phone_type for injecting text, and no stated prerequisites (for example, whether writing needs the app in the foreground).

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