Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Edit Tracker worklog record

tracker_worklog_update
Idempotent

Edit a Tracker issue worklog record to change logged duration, comment, or both; use a record ID from worklog_list and get the updated entry.

Instructions

Edit a worklog record on a Tracker issue (duration and/or comment).

Get record_id from worklog_list. Returns the updated record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesTyped request body for ``PATCH /issues/{key}/worklog/{record_id}`` (edit an entry).
issue_keyYesIssue key, e.g. QUEUE-123.
record_idYesWorklog record id, from ``worklog_list``.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.122.1
    • 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",
-  "record_id",
-  "body"
-]New value: +[
+  "issue_key",
+  "record_id",
+  "body"
+]
  2. First observedv0.67.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, covering the safety and idempotency profile. The description adds that the operation edits duration and/or comment and returns the updated record, which is useful since no output schema exists, but it does not mention auth requirements, permissions, or rate limits.

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 short sentences with no wasted words. The purpose is front-loaded, followed by the prerequisite and return value. Every sentence 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?

The description covers what the tool does, how to obtain the record_id, and that it returns the updated record. Given the rich schema and annotations, this is nearly complete, though it could say more about the response shape or permissions needed for editing.

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 fully documents issue_key, record_id, and the body fields. The description's mention of 'duration and/or comment' slightly clarifies that either or both fields may be updated, but it largely repeats what the schema already provides. Baseline 3 is appropriate.

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?

The description states a specific verb ('Edit') and resource ('a worklog record on a Tracker issue'), making the tool's purpose immediately clear. It also names the editable fields (duration and/or comment). It does not explicitly differentiate itself from siblings like tracker_worklog_create or tracker_worklog_delete, but the action is unambiguous.

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

Usage Guidelines3/5

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

The description gives a prerequisite (get record_id from worklog_list) but does not state when to use this tool versus alternatives such as worklog_create or worklog_delete. Usage is implied by the verb 'Edit', but there are no explicit inclusion/exclusion rules.

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