dialogbrain

clipboard_copy

Read-onlyIdempotent

Copy a secret (a Telegram bot token, a password someone sent in a chat, a browser identity's sign-in password) WITHOUT seeing it, to paste it into a tool in this or another workspace.

Returns a handle clip:<id>, never the value. Pass the handle where a tool's parameter says it takes one: channels.connect_telegram_bot(bot_token="clip:...", in_workspace=), browser.create_identity(password="clip:...", username=<the copy's username>, origin=<the copy's origin>, in_workspace=), channels.connect(channel='email', credentials={..., password="clip:..."}). The server puts the secret in for that run and takes it out of the answer; any other parameter refuses a handle.

source, exactly one of:

{message_id, pattern?}: a token inside a message, by its numeric id from messages.read_history; pattern 'telegram_bot_token' (the default: BotFather's answer) or 'password' (a message that is the password alone, one word with no spaces).
{channel_account_id}: a connected Telegram bot's token. A bot still connected in another workspace is refused there until it is disconnected: a bot has one webhook.
{identity_id}: the password a browser identity signs in with (browser.list_identities). The answer also names its origin and username (not secrets); the password is pasted only for that same origin.

Rules: owner or admin of the workspace the secret is in, and of the workspace it is pasted into; the handle is yours alone, lasts 15 minutes and is spent by the first run that succeeds with it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source": "<source>"
    },
    "name": "clipboard_copy"
  }
}

Input Schema

Name	Required	Description	Default
`source`	Yes	Where the secret is: {message_id, pattern?} \| {channel_account_id} \| {identity_id}.
`in_workspace`	No	Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedInput schema / properties / source / description

Previous value: -"Where the secret is: {message_id, pattern?} | {channel_account_id}."New value: +"Where the secret is: {message_id, pattern?} | {channel_account_id} | {identity_id}."

AddedNov 9, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well past the annotations by disclosing authorization (owner or admin of both the source and target workspace), handle lifetime ('lasts 15 minutes'), single-use semantics ('spent by the first run that succeeds'), and that handles are per-user. There is mild tension between 'spent by the first run' and idempotentHint=true, but that concerns consuming the handle in another tool rather than repeating this call, so it is not a contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The handle/return contract is front-loaded and the source variants are cleanly bulleted. It is dense and slightly repetitive (the 'pass the handle where a parameter takes one' rule is restated through three examples), which costs a point but not readability.

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?

For a tool with a nested source object and no output schema, everything an agent needs is present: what is returned (a handle, never the secret), how to redeem it, expiry, permission requirements, and failure modes. Nothing material is left to inference.

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

Parameters5/5

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

Although schema coverage is 100%, the description supplies semantics the schema cannot: the three mutually exclusive source shapes, the fact that message_id comes from messages.read_history, the undocumented pattern values ('telegram_bot_token' default, 'password' meaning a one-word message), and what channel_account_id and identity_id actually resolve to.

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?

Opens with a specific verb and resource ('Copy a secret ... WITHOUT seeing it') and states the return contract immediately ('Returns a handle `clip:<id>`, never the value'). This is clearly distinguishable from the sibling agents_* toolset, since it is the only indirection/handle-producing operation described.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains exactly where the handle is consumed and shows three concrete call sites (channels.connect_telegram_bot, browser.create_identity, channels.connect) with parameter placements. It also states the negative case: 'any other parameter refuses a handle', and the refusal condition when a bot is still connected in another workspace.

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

All dialogbrain tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.