Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Add Tracker checklist item

tracker_checklists_create

Add an item to a Tracker issue checklist, creating the checklist if it doesn't exist. Returns the issue with its full checklist.

Instructions

Add an item to a Tracker issue's checklist (creates the checklist if absent).

Returns the issue with its full checklist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesTyped request body for ``POST /issues/{key}/checklistItems`` (add an item).
issue_keyYesIssue key, e.g. QUEUE-123.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.122.1
    • changedInput schema / properties / body / properties / deadline / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "description": "Typed ``deadline`` block for a checklist item or key result write body.",
-    "properties": {
-      "date": {
-        "description": "Deadline date, YYYY-MM-DDThh:mm:ss.sss±hhmm.",
-        "type": "string"
-      },
-      "deadlineType": {
-        "default": "date",
-        "description": "Deadline kind: 'date' or 'quarter'.",
-        "type": "string"
-      }
-    },
-    "required": [
-      "date"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "description": "Typed ``deadline`` block for a checklist item or key result write body.",
+    "properties": {
+      "date": {
+        "description": "Deadline date, YYYY-MM-DDThh:mm:ss.sss±hhmm.",
+        "type": "string"
+      },
+      "deadlineType": {
+        "description": "Deadline kind: 'date' or 'quarter'.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "date",
+      "deadlineType"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / issue_key
      Added value: +{
+  "description": "Issue key, e.g. QUEUE-123.",
+  "type": "string"
+}
    • removedInput schema / properties / key
      Removed value: -{
-  "description": "Issue key, e.g. QUEUE-123.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "key",
-  "body"
-]New value: +[
+  "issue_key",
+  "body"
+]
  2. First observedv0.67.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the bar is lower. The description still adds value: it discloses the checklist-creation side effect and states that the return payload is the issue with its full checklist, which the annotations do not convey.

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, no filler, with the primary action front-loaded and the side effect/return noted second. Every clause earns its place.

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 2-parameter nested-body write tool with no output schema, the description covers the mutation's side effect and the return shape. It leaves minor gaps (permission requirements, whether repeat calls append duplicate items given idempotentHint=false), but nothing essential for correct invocation is missing.

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 description coverage is 100%, with body.text, checked, assignee, and the nested deadline block all documented inline, so the baseline of 3 applies. The description adds no additional meaning about issue_key format or body semantics beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb (add) plus resource (checklist item on a Tracker issue) and it names the side effect of creating the checklist when absent. It does not, however, distinguish itself from the near-identically named sibling tracker_entities_checklists_create, which is a real ambiguity for an agent scanning this list.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives (tracker_checklists_update, tracker_checklists_clear, tracker_entities_checklists_create). The parenthetical about creating the checklist if absent implies an upsert-style behavior but gives no explicit routing guidance.

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

Deploy Server

Other Tools