clippy

Set Clippy Room Password

set-room-password-tool

Lock or unlock a Clippy room. Requires the room owner_token (returned by create-room). Pass a password to lock the room; pass an empty password to remove the lock. Only the owner can change this.

Input Schema

TableJSON Schema

Name	Required	Description
`room`	Yes	The 6-character room code (or a Clippy share URL / #CODE link).
`password`	No	The new password to lock the room with. Pass an empty string to remove the password and make the room open.
`owner_token`	Yes	The room owner_token proving you own this room. Required.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`code`	Yes	The room code whose lock state changed.
`locked`	Yes	Whether the room is now password-protected.

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It discloses locking/unlocking behavior and owner restriction, but does not describe potential side effects (e.g., impact on connected users) or safety 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?

The description is two clear, front-loaded sentences. Every word adds value: purpose, method, and constraints—no redundancy.

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?

Given the tool's simplicity (3 parameters, output schema exists), the description covers the essential logic. It could mention error handling, but overall sufficient for correct invocation.

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 coverage is 100%, so baseline is 3. The description repeats the schema information (password to lock/unlock) without adding new semantic value beyond what's already in the parameter descriptions.

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 clearly states the tool locks or unlocks a Clippy room, using specific verbs and resource. It distinguishes itself from sibling tools like room-status (read-only) or clear-room (different action) by focusing on password management.

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 explains the prerequisites (requires owner_token from create-room) and the ownership constraint ('Only the owner can change this'). While it doesn't explicitly mention when not to use or alternatives, the usage context is well-defined.

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?