Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Log time on a Task, User Story, or Bug

log_time

Record hours worked against a Task, User Story, or Bug with a date and work summary. Use it to capture time after finishing a task or at the end of a work session.

Instructions

Log time spent working on a Task, User Story, or Bug. Call this after completing a task or at the end of a work session.

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": {
      "entityId": "<entityId>",
      "entityType": "<entityType>",
      "hours": "<hours>"
    },
    "name": "log_time"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoISO date string, defaults to today (e.g. "2024-05-21")
hoursYesHours spent (can be decimal e.g. 1.5)
entityIdYesID of the Task, User Story, or Bug to log time against (e.g. 145789)
entityTypeYesType of the entity
descriptionNoWhat was done — brief summary of the work

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the entire behavioral burden. It signals a write operation only implicitly through 'log', and never states permissions required, whether entries are editable or removable afterward, whether hours are capped or validated against a work calendar, or what a successful call returns.

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, zero filler, and the core purpose is front-loaded ahead of the timing advice. Nothing could be removed without losing information.

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

Completeness2/5

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

This is a five-parameter mutation tool with no annotations and no output schema, so the description must cover the write semantics itself. It explains what the tool does and when to call it, but omits success/error behavior, permission prerequisites, and whether the entityType must match the actual entity — meaningful gaps for a write operation.

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 each of the five parameters documented in the schema (ISO date defaulting to today, decimal hours, entity ID format, entity type enum, work summary). The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 uses a specific verb and resource ('Log time spent working on') and enumerates the supported entity types, which mirrors the entityType enum. It is immediately distinguishable from read-oriented siblings such as get_my_time_logs, though it never names the counterpart explicitly.

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

Usage Guidelines4/5

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

It gives explicit timing guidance: 'Call this after completing a task or at the end of a work session.' That resolves the main when-to-use question. It stops short of stating when not to use it or whether duplicate entries for the same work session are permitted.

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