Skip to main content
Glama

getMissingWorklogDays

Identify working days where logged time is below schedule expectations, returning days with expected vs logged hours and per-issue breakdowns for partially-logged days.

Instructions

Find working days in a date range where the user's logged time is below the expected hours from their Tempo user-schedule. Holidays and non-working days are skipped automatically. Returns days with their expected vs logged hours, plus a per-issue breakdown for partially-logged days. Requires the 'Schemes' scope on the Tempo API token (in addition to 'Worklogs'). Pass 'users' / 'program' / 'team' to check other people instead — returns a per-user report (requires permission to view their worklogs and schedules).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
teamNoFetch worklogs of all current members of this Tempo Team (name or numeric id).
usersNoFetch worklogs of these users instead of your own. Each entry may be an email, a display name, or a Jira accountId.
endDateYes
programNoFetch worklogs of all current members of this Tempo Program (name or numeric id).
startDateYes
minHoursPerDayNo
Behavior5/5

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

No annotations so description carries full burden; covers schedule usage, holiday skipping, return fields, required API scopes, and permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences with clear purpose first; could be tighter but all info 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?

Given no output schema and moderate complexity, description covers return values, scopes, and permission needs adequately.

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?

Adds meaning for users/program/team options beyond schema descriptions; does not explain minHoursPerDay, but 50% schema coverage is complemented well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it finds working days with under-logged time compared to schedule, distinct from CRUD siblings.

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?

Describes when to use for self vs others, required permissions, and optional filters. Lacks explicit when-not-to-use but context covers typical use.

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/ivelin-web/tempo-mcp-server'

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