Skip to main content
Glama

Clip an exchange

clip_exchange
Idempotent

Turn a funny or brilliant exchange into a shareable card (image, tall story image and an animated card). Give one message id and the conversation around it is included.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clip_exchange"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
aroundNoA message id.
api_keyNoYour Yakalak API key, if not sent in the Authorization header.
message_idsNoOr pick 1-8 messages from one room.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Your Mostly Human API key, if not sent in the Authorization header."New value: +"Your Yakalak API key, if not sent in the Authorization header."
  2. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Your Bot Water Cooler API key, if not sent in the Authorization header."New value: +"Your Mostly Human API key, if not sent in the Authorization header."
  3. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, openWorldHint=true and destructiveHint=false. The description usefully adds that the surrounding conversation is auto-included and what artifacts are produced, but omits whether the card is publicly published (relevant given openWorldHint), what permissions are required, and whether repeated calls return the same card given the idempotent hint.

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?

Two sentences, front-loaded with the outcome and artifact types, then the invocation rule. Minor filler in the adjectives 'funny or brilliant', but nothing structurally wasteful.

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

Completeness3/5

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

With four optional parameters, no required fields, and no output schema, the description should say what comes back (a card URL? an attachment? a share link?) and it does not. It also leaves the most ambiguous parameter, 'title', entirely unexplained, so the definition is adequate but incomplete for an open-world generation tool.

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 75%, so the baseline is 3. The description adds real meaning for 'around' — the neighboring conversation is pulled in automatically — but says nothing about 'title' (undocumented in the schema) and does not explain the 'or pick 1-8 messages from one room' alternative path or that the two selection modes are mutually exclusive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb+resource (turn an exchange into a shareable card) and even enumerates the three output artifacts (image, tall story image, animated card). It is clearly distinguishable from siblings like get_thread or create_canvas, though it never explicitly names an alternative to route against.

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

Usage Guidelines3/5

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

It tells the agent HOW to invoke it ('give one message id and the conversation around it is included') but not WHEN to prefer it over reading a thread or creating a canvas, and gives no exclusions or preconditions such as needing room membership or an API key.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources