Skip to main content
Glama
Sign In
ops-brain

ops-brain

by TheK3nsai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

accept_handoff

Claim a pending handoff and record the accepting agent so interrupted work can resume across AI agents.

Instructions

Claim a pending handoff and record its acceptor. Bound tokens use their own identity; family credentials and unbound broadcast claims require a concrete agent_name. Follow with complete_handoff.

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": {
      "handoff_id": "<handoff_id>"
    },
    "name": "accept_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_nameNoConcrete acceptor identity. Required for family credentials and for unbound/stdio broadcast claims. Fixed agent tokens record their bound identity; a supplied name must match the fixed identity or family.
handoff_idYesHandoff ID (UUID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false / idempotentHint=false / destructiveHint=false, so the mutation profile is already covered. The description adds the identity-resolution behavior and the follow-up step, but says nothing about what happens if the handoff is already claimed, not pending, or how failures surface for a non-idempotent state transition.

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

Conciseness5/5

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

Two tight sentences: the core action leads, the conditional parameter rule follows, and the next-step tool is last. No filler and nothing redundant.

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?

For a 2-parameter state-transition tool with no output schema, the description covers purpose, the conditional identity rule, and the follow-up call. It is missing only edge-case behavior (non-pending/already-claimed handoffs), which is a minor gap given the annotations already signal a non-idempotent write.

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 100%, so both parameters (handoff_id, agent_name) are fully documented in the schema. The description's rules for agent_name restate the same requirement already in the schema field description, adding little beyond the baseline.

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+resource ('Claim a pending handoff and record its acceptor'), which is clearly distinguishable from create_handoff, get_handoff and delete_handoff. It does not explicitly contrast itself with those siblings, but the transition semantics are unambiguous.

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?

Provides a concrete rule for when agent_name is needed (family credentials, unbound/stdio broadcast claims) versus bound tokens. It also names the required follow-up tool (complete_handoff), giving the agent the workflow context. No explicit exclusion of alternatives such as complete_handoff, but the sequencing is clear.

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