idea-base-mcp-server

Official

Overview Schema Source Related Servers Discussions Admin

remove_assignee

Removes one user's assignment from a task, leaving other assignees untouched. Use for full unassignment, not ending a work session.

Instructions

Remove exactly one user's assignment from a task, leaving every other assignee untouched. DELETE /api/tasks/:id/assignments?user_id=... removes that one task_assignments row outright (both the assignment and any is_active flag on it) — this is a full unassign, not stop_working's "still assigned, no longer active" (use stop_working to end a work session without unassigning).

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>",
      "user_id": "<user_id>"
    },
    "name": "remove_assignee"
  }
}

Input Schema

Name	Required	Description	Default
`task_id`	Yes	The ID of the task to remove the assignment from.
`user_id`	Yes	User ID to remove from the task's assignees.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.2.0Oct 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and mostly does: it discloses the underlying DELETE endpoint and that the task_assignments row (plus its is_active flag) is removed outright, making the destructive, non-reversible nature clear. It does not mention required permissions or auth, which is the only notable gap.

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?

Front-loaded with the core action and the count constraint, followed by the mechanism and the sibling contrast. The endpoint path is slightly verbose but it earns its place by clarifying the deletion semantics.

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-param mutation tool with no output schema, the description covers action, scope, mechanism, and sibling disambiguation well. Only auth/permission expectations are missing, which is a minor gap rather than a blocking one.

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 both parameters are already documented in the schema. The description adds only mild value by showing user_id as a query parameter and task_id in the path, so the baseline 3 applies.

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?

States a specific verb (remove) and resource (one user's assignment on a task) with precise scope — exactly one assignee, others untouched. It distinguishes itself from the sibling stop_working by contrast, so an agent can route correctly without opening either schema.

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?

Explicitly names the alternative (stop_working) and the condition that selects it: use stop_working to end a work session without unassigning. This is a clear when-to-use-this vs when-to-use-that statement.

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