Simpler.Asia

team_assignment_accept

Accepts a pending job — only the assignee may call this, and only while the assignment is still 'pending'; it stamps accepted_at and moves status to 'accepted'. NEXT: team_assignment_start once you begin the work.

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_accept"
  }
}

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/5.0

Behavior4/5

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

Annotations establish non-read-only, non-idempotent, non-destructive behavior; the description adds permission (assignee only), state guard (pending only), and exact side effects (accepted_at stamped, status becomes accepted). It does not discuss failure modes or return payload, but with annotations this is strong.

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 compact sentences, front-loaded with the action and preconditions; the next-step pointer earns its place. No repetition or filler.

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?

Core action semantics and preconditions are complete, and annotations cover the safety profile. However, for a tool exposing 22 parameters, the description is silent on which parameters matter when invoking accept, leaving a gap around schema usage.

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

Parameters1/5

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

Schema description coverage is 5% across 22 parameters, and the description adds no parameter guidance at all. It neither mentions the required id nor explains the role of the other 21 fields, leaving the schema's undocumented parameters unaddressed.

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 action ('accepts a pending job') on a specific resource and constrains it to the pending state and assignee. Names the follow-on sibling team_assignment_start, so it is clearly distinguishable from start/decline/complete.

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 says only the assignee may call it and only while status is pending, giving both actor and state preconditions. It also points to team_assignment_start as the next step once work begins.

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?