mcp-agent-hub

my_assignments

Retrieve the tasks assigned to the current subagent, excluding completed work by default, to track active responsibilities and plan next actions.

Instructions

子代理：查看分配给自己的任务（默认不含已完成）。

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

Input Schema

Name	Required	Description	Default
`agent`	No
`include_done`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 27, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the default filtering behavior (excludes completed), but says nothing about permissions, whether other agents' assignments are visible, or result ordering/limits.

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?

A single short sentence with the key scoping detail front-loaded and no filler. It is efficient, though perhaps terse enough to leave the agent param ambiguous.

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?

An output schema exists so return values need not be explained, and the core behavior is covered. However, the undocumented 'agent' parameter and the absence of sibling routing leave meaningful gaps for a tool with 0% schema coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for both parameters. The description explains the include_done default, but the 'agent' parameter is left unexplained and arguably conflicts with the 'assigned to oneself' phrasing, leaving the reader unsure whether it can target other agents.

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?

The description states a specific verb+resource ('查看分配给自己的任务' – view tasks assigned to oneself) with a clear scope qualifier (default excludes completed). It is distinguishable from sibling list_tasks, though it doesn't name that sibling explicitly.

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 context is implied by the '子代理' (sub-agent) framing and the default-excludes-done note, but there is no explicit statement of when to prefer this over list_tasks or claim_task. The reader must infer the alternative.

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