Skip to main content
Glama

clippy

by io.github.IDTitanium

Store Image in Clippy Room

store-image-tool

Post one or more images (PNG, JPEG, GIF, or WEBP) to a Clippy room so they appear on every device watching it, optionally with a text caption. Pass each image as a base64 string or a data: URI. The room is created if it does not exist. Subscribed devices get a push notification. Returns the stored item, including direct URLs to fetch each image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomYesThe 6-character room code (or a Clippy share URL / #CODE link). The room is created if new.
textNoOptional caption to store alongside the image(s). Up to 200,000 characters.
deviceNoOptional short label for who is posting (max 64 chars). Defaults to "AI Agent".
imagesYesOne or more images, each a base64-encoded PNG/JPEG/GIF/WEBP or a data: URI (e.g. "data:image/png;base64,iVBOR..."). Up to 10 images, 10 MB each.
passwordNoRequired only if the room is password-protected and you are not using owner_token.
owner_tokenNoOptional. The room owner_token; bypasses the password on a locked room.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesHuman-shareable URL that opens the room on any device.
codeYesThe room code the image was stored in.
itemYesThe stored item, including image URLs.

TDQS

A4.2/5.0
Behavior4/5

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

With empty annotations, the description carries the full burden. It discloses that the room is created if not existing, subscribed devices get push notifications, and the return includes direct URLs. This provides useful behavioral context beyond the raw schema.

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 concise (5 sentences, ~80 words), front-loaded with the primary action, and each sentence adds distinct value. There is no redundancy or fluff.

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 complexity (6 params, output schema exists, no nested objects), the description covers the main behavioral aspects: posting images, room creation, push notifications, and return format. Minor omissions like failure modes or rate limits prevent a perfect 5.

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 adds minimal extra meaning: it restates that images are passed as base64 or data URI, which is already in the schema. It does not clarify parameter interactions or constraints beyond what the schema provides.

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's purpose: 'Post one or more images to a Clippy room so they appear on every device watching it, optionally with a text caption.' It also distinguishes from siblings by specifically targeting images, while a generic store-item-tool exists.

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 clearly indicates when to use this tool (to post images to a Clippy room) and provides context like room creation and push notifications. However, it does not explicitly state when not to use it or what alternatives exist (e.g., store-item-tool for non-image items).

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

All clippy toolsInspect
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