clippy

Store Item in Clippy Room

store-item-tool

Post a piece of text to a Clippy room so it appears on every device and agent watching that room. The room is created automatically if it does not exist yet. Subscribed devices receive a push notification. This is how you "send" something to a user or leave a note for another agent. Returns the stored item.

Input Schema

TableJSON Schema

Name	Required	Description
`room`	Yes	The 6-character room code (or a Clippy share URL / #CODE link). The room is created if new.
`text`	Yes	The text content to store (a snippet, link, message, etc.). Up to 200,000 characters.
`device`	No	Optional short label for who is posting (max 64 chars). Defaults to "AI Agent" so humans can tell agent posts apart.
`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
`url`	Yes	Human-shareable URL that opens the room on any device.
`code`	Yes	The room code the item was stored in.
`item`	Yes	The stored item.

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description fully covers behavior: room creation, push notifications, default device label, character limit, password/owner_token usage, and return value. No contradiction with 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?

The description is succinct (one paragraph), front-loaded with purpose, and every sentence adds useful information without redundancy.

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

Completeness5/5

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

Given the complexity (5 parameters, many sibling tools) and the presence of an output schema, the description provides sufficient context for correct usage and disambiguation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds value by explaining room format (6-character code or URL), device default ('AI Agent'), and the role of password vs owner_token. This goes beyond the schema 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 posts text to a Clippy room, distinguishing it from sibling tools like store-image-tool (for images) and update-item-tool (for modifying existing items). The verb 'store' and resource 'text to room' are specific.

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 explains this tool is for sending messages to users or leaving notes for agents, and mentions automatic room creation and push notifications. However, it does not explicitly contrast with alternatives like store-image-tool or when to use the device label.

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?