Skip to main content
Glama
Sign In
macos-agent-bridge

macos-agent-bridge

by juliusloon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

clipboard_read

Read-onlyIdempotent

Reads the current plain-text clipboard contents for macOS agent workflows; it does not import Raycast Clipboard History.

Instructions

Read current plain-text clipboard only. Does not import Raycast Clipboard History. [v1.0.0; permissions: none]

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYes
toolYestool name
errorYes
statusYes
versionYessemantic version

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description still adds real value beyond them: plain-text-only format limitation, 'current' versus history scope, and 'permissions: none' as an auth requirement.

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?

Two short sentences, front-loaded with the action and scope constraint. The bracketed '[v1.0.0; permissions: none]' tag is partly useful (permissions) but the version string is filler that slightly dilutes the signal.

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?

With an output schema present, return values need no explanation, and annotations carry the safety profile. Scope, format limitation, and auth needs are all covered, leaving nothing an agent needs in order to call this correctly.

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?

The tool takes zero parameters, so the baseline is 4 and there is no parameter semantics to document. The description correctly implies a no-argument call and adds no misleading parameter hints.

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?

States a specific verb and resource ('Read current plain-text clipboard') and narrows scope with 'only', which separates it from history-import behavior. It does not name the sibling clipboard_write, so the differentiation is scope-based rather than explicit routing.

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?

'Does not import Raycast Clipboard History' is an effective when-not boundary that tells the agent this tool is not the path for history retrieval. There is no positive statement of when to prefer it over alternatives such as system_get_selected_text, so the guidance stops just short of full routing.

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