Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Add Tracker entity checklist items

tracker_entities_checklists_create

Add checklist items to a Tracker entity (project, portfolio, or goal) and return the updated entity with its checklist.

Instructions

Add checklist item(s) to a Tracker entity; returns the entity with its checklist.

body is a bare array of items, e.g. [{"text": "…"}].

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesA bare array of checklist items.
expandNoExtra blocks to include in the reply.
fieldsNoComma-separated fields to include in the reply.
notifyNoNotify the users in the fields of the object; omitted, the API notifies.
entity_idYesEntity id (or shortId).
entity_typeYesEntity type: ``project``, ``portfolio`` or ``goal``.
notify_authorNoNotify the author of the change; omitted, the API does not.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.122.1
    • changedInput schema / properties / body / items / 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"
+  }
+]
  2. First observedv0.67.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description usefully adds return behavior ("returns the entity with its checklist") but says nothing about permissions, duplicate handling, or side effects such as notifications (which are in the schema, not the description).

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 with zero waste. The core action is front-loaded, and the body-format note follows as a secondary clarification.

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?

For a 7-parameter mutation tool with no output schema, the description covers the action and the return shape, and annotations cover the safety profile. However, it omits error conditions, permission requirements, and behavior around the notify/notify_author options that materially affect invocation.

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%, so the schema already documents all 7 parameters, including the body array and its item shape. The description's `[{"text": "…"}]` example is a mild reinforcement of what the schema already states, meriting the baseline 3.

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?

States a specific verb and resource ("Add checklist item(s) to a Tracker entity") and clarifies the target entity type. It does not explicitly differentiate from siblings like tracker_entities_checklists_update or tracker_entities_checklists_items_update, but the create semantics are unambiguous.

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 explicit when-to-use or when-not-to-use guidance, and no alternative sibling is named. The only hint is the body example (`[{"text": "…"}]`), which implicitly signals the create case versus edit-all, but that is inference rather than 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