clippy

Clear Clippy Room

clear-room-tool

Destructive

Delete ALL items in a Clippy room (and their images). Use with care — this wipes everything shared in the room and cannot be undone. The room itself continues to exist and can be reused.

Input Schema

TableJSON Schema

Name	Required	Description
`room`	Yes	The 6-character room code (or a Clippy share URL / #CODE link).
`password`	No	Required only if the room is password-protected and you are not using owner_token.
`owner_token`	No	Optional. The room owner_token; bypasses the password on a locked room.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`code`	Yes	The room code that was cleared.
`cleared`	Yes	Number of items that were deleted.

TDQS

A4.4/5.0

Behavior5/5

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

The description adds significant context beyond annotations: it discloses that images are also deleted, that the action cannot be undone, and that the room itself persists. This complements the destructiveHint annotation with specific behavioral details.

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 sentences with no fluff. The first sentence clearly states the action and scope; the second provides critical warnings. Highly efficient and well-structured.

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 description covers the essence: what is deleted, what remains, and the irreversible nature. With an output schema available, it does not need to detail return values. It lacks mention of errors or edge cases, but given the tool's simplicity, it is sufficiently complete.

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 parameters are fully documented there. The description adds no extra explanation about parameters, which is acceptable but does not improve understanding beyond the schema.

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 'Delete ALL items in a Clippy room (and their images)', clearly specifying the verb and resource. It distinguishes from siblings like delete-item-tool by indicating it deletes everything.

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?

The description includes a warning 'Use with care — this wipes everything shared in the room and cannot be undone', implying it should be used only when intentionally clearing the room. It does not explicitly name alternatives but context with siblings (e.g., delete-item-tool for single items) provides enough guidance.

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

All clippy tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: room creation, text/image storage, item listing, deletion, password management, and room status checking. No two tools overlap in functionality; descriptions make the differences obvious.

Naming Consistency5/5

All tool names follow a consistent kebab-case verb-noun-tool pattern (e.g., clear-room-tool, store-item-tool), making the naming predictable and easy to understand.

Tool Count5/5

With 9 tools, the server covers the core operations needed for a shared clipboard room without being excessive or too sparse. Each tool serves a necessary function in the workflow.

Completeness5/5

The tool set provides full lifecycle coverage: create room, store text/images, list items, update text, delete individual/clear all items, set password, and check room status. No obvious gaps for the intended domain.

Resources

Need Help?