Skip to main content
Glama
Sign In
musterd

musterd

Official
by musterd-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

lane_handoff

Transfer a lane and its branch to another seat so work arrives as an artifact. Add the handoff reason in one note; eligible offline recipients can be woken.

Instructions

Hand a lane to another seat with its branch, so work arrives as an artifact. Put the why in note — it rides the same act, so no second send. Wake-eligible if they are offline + host-enrolled.

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": {
      "id": "<id>",
      "to": "<to>"
    },
    "name": "lane_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYeslane id
toYesrecipient seat
noteNowhy you are handing it over
branchNobranch carrying the work

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose meaningful behavior: the work arrives as an artifact, the note is delivered atomically with the handoff, and the recipient can be woken if offline and host-enrolled. Missing are whether the sender loses the lane, whether the handoff is reversible, and any permission prerequisites for a mutation of this weight.

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 tight sentences with the core action front-loaded and no filler. The density comes at a small cost: 'wake-eligible' and 'host-enrolled' are compressed to the point of ambiguity.

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?

There is no output schema or annotations, so the description is the only behavioral source, and it covers the transfer, the note, and wake behavior. It leaves gaps on ownership transfer semantics, reversibility, and error conditions that an agent handing off a lane would want to know.

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 all four parameters are already documented, which sets the baseline at 3. The description adds some meaning by framing 'note' as the rationale that rides the same act and 'branch' as the carrier of the work, but adds nothing about 'id' or 'to' beyond the schema.

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: hand a lane to another seat, including the branch as a carried artifact. An agent can distinguish this from lane_release or lane_claim. It falls short of 5 because 'seat' and 'host-enrolled' are domain jargon that a fresh agent must infer.

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?

Usage is implied rather than stated: 'no second send' implicitly steers away from team_send, and 'put the why in note' tells the agent how to use it. But no sibling tool is named explicitly, and there is no statement of when NOT to hand off (e.g., versus lane_release or lane_update).

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

Deploy Server

Other Tools