Simpler.Asia

team_assignment_undo_reassign

Reverts an assignment's most recent reassignment — restores the previous assignee and status. Only the person who performed that reassignment may call it, and only within the 30-second window after it happened; past that, CONFLICT says to reassign again instead.

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

Input Schema

Name	Required	Description
`id`	Yes	The team_assignment id (team_assignment_list shows them).
`title`	No
`due_at`	No
`status`	No
`priority`	No
`started_at`	No
`accepted_at`	No
`artifact_id`	No
`assigned_to`	No
`declined_at`	No
`description`	No
`photos_json`	No
`completed_at`	No
`reassigned_at`	No
`reassigned_by`	No
`attachment_key`	No
`decline_reason`	No
`attachment_name`	No
`attachment_type`	No
`previous_status`	No
`completion_notes`	No
`previous_assignee`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only cover the generic safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false); the description adds substantive context the annotations cannot: a caller-identity authorization rule, a hard 30-second time-to-live, and the specific CONFLICT failure path with the recommended recovery. That is exactly the behavioral disclosure an agent needs before invoking.

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 sentences, zero filler, with the effect front-loaded and the authorization/timing constraints following. Every clause carries distinct information.

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 mutation with no output schema, the description covers effect, authorization, timing and failure recovery well. The remaining gap is the large optional payload inherited from the assignment schema, which is left unexplained.

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 description coverage is 5% — only `id` is documented — and the description offers no parameter guidance at all. It implicitly suggests the previous assignee/status are server-tracked history rather than inputs, but it never states that the other 21 optional fields (title, status, priority, reassigned_by, etc.) are ignored on this call, leaving an agent to guess whether it should pass them.

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 and resource ("Reverts an assignment's most recent reassignment") and immediately names the effect ("restores the previous assignee and status"), which cleanly separates it from sibling team_assignment_reassign.

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?

Gives explicit preconditions ("Only the person who performed that reassignment may call it") and an explicit exclusion with an alternative ("only within the 30-second window... past that, CONFLICT says to reassign again instead"). An agent knows exactly when to call this versus its sibling.

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

All Simpler.Asia tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?