Skip to main content
Glama
Sign In

CheckFlow

by io.checkflow
OverviewDiscussionsAdmin

Clear task assignees

clear_task_assignees
Idempotent

Unassign a task from everybody. The same write as set_task_assignees with an empty list, and it exists because clearing is worth being able to ask for without composing one. A task assigned to nobody is open to everybody who can run the checklist, whatever isAssignedExclusively says.

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": {
      "checklistKey": "<checklistKey>",
      "taskKey": "<taskKey>"
    },
    "name": "clear_task_assignees"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskKeyYesThe task's key, a GUID.
checklistKeyYesThe checklist's key, a GUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover idempotency and non-destructiveness, so the bar is lower, but the description adds real business semantics: after clearing, the task is open to everyone who can run the checklist regardless of isAssignedExclusively. That is a consequence an agent would not infer from structured fields. It stops short of noting permissions required to clear others' assignees.

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?

Three short sentences, lead sentence front-loaded with the action, then the alternative, then the consequence. The middle rationale clause is slightly wordy but earns its place by justifying the tool's separate existence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-required-parameter mutation with full schema coverage and annotations covering idempotency and destructiveness, nothing an agent needs to call it correctly is missing; the semantic outcome is even spelled out.

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% with both required GUID parameters documented in the schema, so the baseline applies. The description adds no format, constraint, or meaning beyond what checklistKey and taskKey already carry.

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 ('Unassign a task from everybody') and explicitly contrasts itself with the sibling set_task_assignees, so an agent can route between the two 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?

Names the alternative ('the same write as set_task_assignees with an empty list') and gives the condition that selects this tool ('clearing is worth being able to ask for without composing one'). When-to-use and the equivalent-alternative are both explicit.

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

All CheckFlow toolsInspect
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