Lists recent clipboard history across Mac and Windows devices, newest first, with optional count and device filters to find copied items.
List recent clipboard history across the user's devices, newest first.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many clips to return, 1-50 (default 10) | |
| device | No | Only clips from the device with this name |
Changes observed during successful MCP inspections.
v0.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full burden. It usefully discloses the result ordering (newest first) and cross-device scope, but says nothing about permissions, auth, pagination behavior, or what a returned clip contains.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single well-formed sentence with zero waste, front-loading the action and the scoping/ordering constraints.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-optional-parameter list tool this is close, but with no output schema the description should say what a clip record looks like and how results beyond the limit behave. The absence of sibling differentiation also leaves routing incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so both the limit (1-50, default 10) and device filter are already documented. The description adds no syntax or semantics beyond what the schema provides, making the baseline 3 correct.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource (list clipboard history) with scope qualifiers: across devices and newest-first ordering. It does not, however, distinguish itself from the close sibling get_latest_clip or from search_clips, which an agent must infer.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied: the word 'recent' suggests browsing rather than targeted lookup, but the description never says when to prefer this over search_clips or get_latest_clip, nor any conditions for using it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.