Simpler.Asia

team_assignment_decline

Declines a job — only the assignee, and only while it is 'pending' or 'accepted'; decline_reason is required and is stamped alongside declined_at. Declined is terminal, same as completed: the assignment cannot be edited or reassigned afterward.

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

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?

Beyond the annotations it discloses that decline_reason is mandatory and is stamped alongside declined_at, that the caller must be the assignee, and that declined is terminal — no edit or reassignment afterward. That irreversibility is not derivable from destructiveHint=false, so the description carries real added value.

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, front-loaded with the actor and allowed states, then the required field and the terminality consequence. No filler and nothing buried mid-sentence.

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 an action-style tool with no output schema, it covers who may call it, the valid states, the required input, and the irreversible outcome. It does not say what happens on rejection (error vs no-op) or whether unrelated properties in the 22-field schema are ignored, which is a modest remaining gap.

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 5%, so the description has to compensate, and it does for the two parameters that matter: it names decline_reason as required and explains declined_at as an auto-stamped value. However, the other ~20 properties go unexplained, and its claim that decline_reason is required conflicts with the schema's required list of only ['id'], leaving the agent unsure whether that is interface or runtime validation.

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 ('Declines a job') and immediately scopes it, making it clearly distinct from team_assignment_accept, team_assignment_complete, and team_assignment_reassign. An agent can pick it out of the sibling list without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit preconditions: caller must be the assignee, and the assignment must be in 'pending' or 'accepted'. The complementary alternative (accept instead, or reassign) is implied by the preconditions but never named, which is the only gap.

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?