Skip to main content
Glama

从系统剪贴板粘贴图片

app_paste_clipboard_image

Reads a bitmap screenshot or copied image file from the system clipboard and returns it for avatar cropping or chat attachments.

Instructions

UI 专用:读取系统剪贴板中的位图截图或复制的图片文件,供头像裁剪或聊天附图使用。

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

Input Schema

NameRequiredDescriptionDefault
modeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It implies a read-only clipboard access and non-destructive behavior, but never says what happens when the clipboard is empty or holds a non-image, whether permissions/UI focus are required, or what form the result takes (bytes, path, base64). Those are the traits an agent most needs to know.

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?

One front-loaded sentence: the 'UI 专用' constraint comes first, followed by what is read and why. There is no filler, and the source formats listed are genuinely informative rather than redundant.

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

Completeness3/5

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

For a simple single-parameter tool this is close to adequate, but with no annotations and no output schema the description should say what the call returns and how failures surface (empty clipboard, unsupported format). The mode parameter's effect is also left unexplained, so an agent could call it correctly but not interpret the result confidently.

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?

With one parameter at 0% schema coverage, the description must compensate. The phrases '头像裁剪' and '聊天附图' do map loosely onto the avatar/attachment enum values, which is useful, but it never explains how the two modes differ in output or processing, so the semantic link stays implicit.

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?

The description gives a specific verb and resource — reading a bitmap screenshot or copied image file from the system clipboard — which is concrete and unambiguous. No sibling tool deals with clipboard images, so confusion is unlikely, though the description never explicitly distinguishes itself from file/attachment tools the way a 5 would.

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?

It states the usage context clearly: 'UI 专用' (UI-only) plus the intended scenarios of avatar cropping and chat attachments. That gives an agent a real basis for choosing this tool, but there are no exclusions (e.g. what to do when the clipboard has no image) and no named alternatives.

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