Skip to main content
Glama
zeph-to

@zeph-to/mcp-server

by zeph-to

zeph_clipboard

Copy text to the clipboard on one or all of your devices. Text appears in clipboard history and can be pasted immediately.

Instructions

Copy text to the user's device clipboard. The text will appear in their clipboard history and can be pasted immediately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesText to copy to clipboard
targetDeviceIdNoTarget device ID. Omit to use configured default or send to all devices.

Implementation Reference

  • The tool handler function. It takes 'text' and optional 'targetDeviceId', calls client.sendPush with type 'clipboard', and returns the push ID.
      async ({ text, targetDeviceId }) => {
        try {
          const result = await client.sendPush({
            title: 'Clipboard',
            body: text,
            type: 'clipboard',
            targetDeviceId: targetDeviceId ?? config.deviceId,
          });
          return textResult({ pushId: result.data.pushId });
        } catch (err) {
          return formatToolError(err);
        }
      },
    );
  • Input schema: 'text' (required string) and 'targetDeviceId' (optional string). Annotations: not readOnly, not destructive, openWorldHint true.
    inputSchema: {
      text: z.string().describe('Text to copy to clipboard'),
      targetDeviceId: z.string().optional().describe('Target device ID. Omit to use configured default or send to all devices.'),
    },
  • The registerClipboardTool function that calls server.registerTool with the name 'zeph_clipboard' and its schema/handler.
    export const registerClipboardTool = (server: McpServer, client: ZephApiClient, config: McpServerConfig) => {
      server.registerTool(
        'zeph_clipboard',
        {
          description:
            'Copy text to the user\'s device clipboard. The text will appear in their clipboard history and can be pasted immediately.',
          annotations: {
            readOnlyHint: false,
            destructiveHint: false,
            openWorldHint: true,
          },
          inputSchema: {
            text: z.string().describe('Text to copy to clipboard'),
            targetDeviceId: z.string().optional().describe('Target device ID. Omit to use configured default or send to all devices.'),
          },
        },
        async ({ text, targetDeviceId }) => {
          try {
            const result = await client.sendPush({
              title: 'Clipboard',
              body: text,
              type: 'clipboard',
              targetDeviceId: targetDeviceId ?? config.deviceId,
            });
            return textResult({ pushId: result.data.pushId });
          } catch (err) {
            return formatToolError(err);
          }
        },
      );
    };
  • src/index.ts:60-61 (registration)
    Top-level invocation: registerClipboardTool(server, client, config) wires up the tool into the MCP server.
    registerNotifyTool(server, client, config);
    registerClipboardTool(server, client, config);
  • The sendPush method on ZephApiClient used by the clipboard handler to POST /pushes/send with the title, body, type, and targetDeviceId.
    async sendPush(params: {
      title: string;
      body?: string;
      url?: string;
      type?: string;
      priority?: string;
      targetDeviceId?: string;
      channelId?: string;
      files?: { fileKey: string; fileName: string; fileSize: number; fileType: string }[];
    }): Promise<PushResponse> {
      return this.request<PushResponse>('POST', '/pushes/send', params);
    }
Behavior4/5

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

The description adds context beyond annotations by noting that text appears in clipboard history and can be pasted immediately. This discloses persistence and immediacy, which are not captured by readOnlyHint or destructiveHint. It does not contradict annotations.

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 concise sentences, no fluff. Every word adds value, making it easy to parse quickly.

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 simple tool with 2 parameters and no output schema, the description adequately covers the core function and expected effect. However, it does not mention potential size limits or behavior when targetDeviceId is omitted.

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 baseline is 3. The description does not add any additional meaning beyond what the schema already provides for 'text' and 'targetDeviceId'.

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 explicitly states 'Copy text to the user's device clipboard', clearly identifying the verb and resource. It also explains the effect (clipboard history, immediate paste), distinguishing it from sibling tools like zeph_broadcast or zeph_notify.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or limitations. It only states the basic function, leaving the agent without context for decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zeph-to/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server