Skip to main content
Glama
Sign In
Agent-Comm-Hub

Agent-Comm-Hub

by liuboacean
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

accept_handoff

Accept a task handoff to assume responsibility. The task assignment transfers to the current agent upon acceptance.

Instructions

接受任务交接。只有被请求的 target Agent 可以调用。接受后任务 assigned_to 转移到当前 Agent。

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

Input Schema

NameRequiredDescriptionDefault
task_idYes要接受的任务 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.4.6

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description discloses the effect (assigned_to transfer) and the caller restriction. It is straightforward but could mention potential side effects like notification or state requirements.

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?

Three short sentences, front-loaded with the purpose, no redundant information. Every sentence is meaningful.

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?

Given the low complexity (1 parameter, no output schema), the description is mostly complete. It explains action, caller, and outcome. Missing details like error conditions or state prerequisites, but adequate for the tool's simplicity.

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 the description adds no extra meaning beyond the schema's definition of task_id. Baseline score of 3 is appropriate.

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?

The description clearly states it accepts a handoff, specifies the caller (target Agent), and describes the outcome (assigned_to transfers). This distinguishes it from siblings like request_handoff and reject_handoff.

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?

It explicitly states that only the requested target Agent can call it, providing clear context. However, it does not discuss when not to use it or compare to alternatives beyond that.

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