Simpler.Asia

team_assignment_start

Marks a job as started — only the assignee, and only from status 'accepted'; it stamps started_at and moves status to 'in_progress'. NEXT: team_assignment_add_photo for proof, then team_assignment_complete when done.

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

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 declare safety flags (non-readonly, non-idempotent, non-destructive); the description adds the authorization requirement, the precondition state, and the concrete side effects (stamps started_at, transitions status to in_progress). This is exactly the mutation behavior an agent needs and cannot get from the annotations.

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 front-loaded sentences with zero filler. The precondition comes before the side effect, and the 'NEXT:' marker makes the follow-up sequence scannable.

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 state-machine mutation with no output schema, the description supplies the precondition, authorization, side effect, and follow-up tools. The only unresolved gap is the oversized 22-property schema, which the description leaves fully 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 only 5% and the schema exposes 22 properties, yet the description explains no parameter at all. It never clarifies that the operation is keyed solely on 'id' or whether the other 21 nullable fields are ignored, so it does not compensate for the documentation gap.

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 ('Marks a job as started') and immediately names the exact lifecycle transition it performs. It is unmistakably distinct from siblings like team_assignment_accept and team_assignment_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 states the authorization condition ('only the assignee') and the state gate ('only from status accepted'), then routes the agent forward with named alternatives: team_assignment_add_photo and team_assignment_complete. Both when-to-use and what-comes-next are given.

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?