Skip to main content
Glama

Hand off a temporary Playground

crabrix_handoff
Idempotent

Share a room's secret edit or view links and expiry, including a link for people and an agentLink for another AI agent, only when the user requests sharing.

Instructions

Only when the user requests sharing: return this room's secret edit/view links and expiry: link for people (browser or Crabrix app) and agentLink for another AI agent (remote MCP URL, or crabrix_connect in Crabrix MCP). A view link cannot become editable; separate view access is available only to its creator. No account storage or execution.

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": "crabrix_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare openWorld=true, idempotent=true, destructive=false, but the description adds what they cannot: the returned values are *secret* links with an expiry, and a view link is permanently non-editable. That security/immutability context is the valuable part. It stops short of saying whether repeated calls mint fresh links or reuse the same ones, and the 'No account storage or execution' line is cryptic without more context.

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 permission gate is front-loaded and every clause carries information; there is no filler. The middle sentence is a dense run-on ('link for people (browser or Crabrix app) and agentLink for another AI agent...') that costs a re-read on first pass.

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 correctly takes on the burden of describing returns: link, agentLink, and expiry. For a one-parameter tool that is nearly sufficient; the gaps are the default/omitted behavior of `mode` and whether the returned links are stable across calls.

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 description coverage is 0% and the sole parameter is an edit/view enum, so the description must carry the meaning. It does contrast edit vs view ('a view link cannot become editable; separate view access is available only to its creator'), which is real added semantics, but it never ties that contrast to the `mode` argument by name nor states what happens when it is omitted (required=false).

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?

States a specific verb and resource: return this room's secret edit/view links plus expiry, split into a human 'link' and an agent 'agentLink'. That is enough for an agent to distinguish it from siblings like crabrix_connect or crabrix_status, though 'this room' leans on ambient session state that the description never defines.

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?

Opens with an explicit gate ('Only when the user requests sharing'), which doubles as a when-not rule for the common failure mode of over-sharing. It also names the alternative route ('crabrix_connect in Crabrix MCP') for the agent-link case and states the view-link restriction, so the agent has when, when-not and alternatives.

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