Skip to main content
Glama
gianni1989

timepiece-mcp

by gianni1989

timepiece_get_issue

Read-onlyIdempotent

Retrieve time-in-status data for a Jira issue, showing duration per workflow status with configurable calendar and time unit.

Instructions

Get time-in-status data for a single Jira issue from Timepiece.

Returns how long the issue has spent in each workflow status (e.g. To Do, In Progress, In Review, Done), using a configurable calendar and time unit.

Args: params (GetIssueInput): Validated input containing: - issue_key (str): Jira issue key, e.g. 'PROJ-123' - columns_by (str): 'statusDuration' or 'assigneeDuration' (default: statusDuration) - calendar (Optional[str]): Timepiece calendar ID or name - day_length (str): 'businessDays' or 'calendarDays' (default: businessDays) - view_format (str): 'days', 'hours', 'minutes', 'seconds' (default: days) - statuses (Optional[str]): Comma-separated status IDs to filter - response_format (str): 'markdown' or 'json' (default: markdown)

Returns: str: Time-in-status data as Markdown table (default) or JSON.

Examples: - "How long has PROJ-123 been in each status?" → issue_key='PROJ-123' - "Show PROJ-456 time in status in hours" → issue_key='PROJ-456', view_format='hours' - "Get calendar days for PROJ-789" → day_length='calendarDays'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds details about configurable calendar and time unit, and the response format (markdown/json). It explains what data is returned.

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?

The description is well-structured with Args, Returns, and Examples sections. It is concise, front-loaded with the purpose, and every sentence adds value.

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

Completeness5/5

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

Given the tool's complexity (7 parameters, nested input, no output schema needed), the description covers all necessary aspects: parameters, defaults, return type, and examples.

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?

The schema already provides descriptions for all parameters, achieving high coverage. The description adds examples and default values but does not significantly extend meaning beyond the schema.

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 it gets time-in-status data for a single Jira issue. It specifies the verb and resource, but does not explicitly differentiate from the sibling 'timepiece_get_issue_expanded'.

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?

The description provides examples but lacks explicit guidance on when to use this tool versus alternatives like 'timepiece_get_issue_expanded' or 'timepiece_list_issues'. No when-not or alternative tools mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gianni1989/timepiece-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server