Skip to main content
Glama

gif_handoff

Wrap agent-to-agent handoffs or result reports in a chat GIF by specifying recipient, request, and feeling; returns the message to send through your own channel.

Instructions

When you hand a job to another agent (a subagent, Codex, another Claude session) or report back a result, wrap your message in a GIF the user sees in the chat. Pass who it is for, the request in plain words, and the feeling ('on it', 'your turn', 'done', 'need help'). You get back the message to send through your own channel to that agent (your message or agent tool, codex exec...): gifmate shows it, it does not deliver it. Not limited by the pace of GIFs to the user.

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": {
      "to": "<to>",
      "request": "<request>"
    },
    "name": "gif_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe agent it is for, e.g. 'Codex', 'reviewer subagent'
sourceNoA GIF URL or path, instead of searching the feeling
feelingNoThe tone, searched on GIPHY when no source is givenon it
requestYesThe request or result, in plain words: this is what the other agent acts on

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.10

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations (openWorldHint=true, readOnlyHint=false), the description discloses the key behavioral fact that the tool only renders the GIF and returns text rather than delivering anything, plus that GIPHY is searched when no source is given and that GIF pacing does not throttle the user. It does not describe failure modes or what happens if the GIPHY search finds nothing.

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?

Three sentences, front-loaded with the trigger and the payload guidance, with no filler. The trailing 'Not limited by the pace of GIFs to the user' is terse to the point of being slightly cryptic, and the parenthetical list of channels is dense.

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?

With no output schema, the description usefully explains the return value ('you get back the message to send through your own channel'), covering the biggest unknown for an agent. Minor gaps remain on return format and on what the user-visible GIF post looks like, but nothing needed to invoke it correctly is missing.

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%, so baseline is 3; the description still adds value by enumerating feeling vocabulary ('on it', 'your turn', 'done', 'need help') that is not an enum in the schema, and by framing 'request' as the text the other agent acts on. It could have clarified when to prefer 'source' over 'feeling' more explicitly.

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?

States a specific verb and resource: wrap a handoff/report message in a GIF the user sees in chat. It also pre-empts confusion with delivery siblings by stating 'gifmate shows it, it does not deliver it', which lets an agent distinguish it from gif_send without opening another schema.

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?

Gives a clear triggering context ('when you hand a job to another agent... or report back a result') and names the concrete alternatives for delivery ('your message or agent tool, codex exec...'). It does not explicitly say when to prefer gif_note or gif_send instead, so it stops short of full when/when-not guidance.

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