Skip to main content
Glama
Sign In
omni-dev

omni-dev

by rust-works
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

jira_worklog_add

Adds worklog time to a JIRA issue using JIRA duration format (e.g., 1h 30m, 2d), with optional comment and start time.

Instructions

Log time on a JIRA issue. time_spent accepts JIRA's duration format (e.g., 1h 30m, 2d). Returns YAML {status: ok}. Mirrors omni-dev atlassian jira worklog add.

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": {
      "key": "<key>",
      "time_spent": "<time_spent>"
    },
    "name": "jira_worklog_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesJIRA issue key (e.g., `PROJ-123`).
commentNoOptional plain-text comment.
startedNoISO 8601 timestamp when the work started.
time_spentYesTime spent (e.g., `1h 30m`, `2d`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.39.0
  2. Removedv0.39.0
  3. Changed2 schema fields changedv0.33.0
    • removedInput schema / description
      Removed value: -"Parameters for the `jira_worklog_add` tool."
    • removedInput schema / title
      Removed value: -"WorklogAddParams"
  4. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only discloses the return format (YAML {status: ok}) but not side effects, permissions, or error handling. Minimal behavioral insight beyond the action itself.

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?

Three sentences, each adding unique value: core purpose, format detail, return type and alias. Front-loaded with no redundancy.

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?

Adequate for basic usage, but missing broader context like error handling, optional parameter usage hints (comment, started), and consequences of logging time. Schema covers started description, but description could elaborate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline 3. The description adds value for time_spent by specifying JIRA's duration format, which is not in the schema description. Other parameters have adequate schema descriptions.

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 clearly states 'Log time on a JIRA issue', specifying the verb and resource. It provides format and return info, but does not explicitly differentiate from sibling tools like jira_worklog_list or jira_dev.

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?

No guidance on when to use this tool over alternatives, no prerequisites or exclusions. The mirror reference is not helpful for usage context.

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