MCP Server for Hubstaff time tracking and task management integration
Server has 11 tools with complete schemas and descriptions. Naming follows verb_noun convention (get_, list_, create_). Descriptions are present but generic, most lack context on WHEN to use the tool or dependencies. Parameters are typed and mostly described, but lack constraints (enums, ranges, formats). Output schemas are not documented. Error handling is absent from visible code. Tools are well-composed (single responsibility), but descriptions don't guide LLM selection between similar tools (e.g., create_task vs create_todo distinction is unclear without domain knowledge).
Create a new task in Hubstaff (for projects WITHOUT task integration like Jira/Asana)
Create a new todo in Hubstaff Tasks (for projects WITH task integration like Jira/Asana)
Get total hours spent on a specific project over a date range for a user. Tip: call list_team_members to discover user IDs.
Get lists from a Hubstaff Tasks project (use project_id to find lists for creating todos)
Get time summary for specified team members and date range. Tip: use list_team_members to build the user_ids array.
Get daily time breakdown by project and task for specified user and date. Tip: call list_team_members first to find valid user IDs.
Output schemas not documented. LLMs cannot plan downstream calls or extract required fields (e.g., what fields does list_team_members return? Is there a user_id field for chaining to get_time_breakdown?).
Descriptions lack WHEN/WHY context and dependency hints. E.g., 'List all organization members' doesn't explain that this is a prerequisite for get_time_breakdown. 'Create a new task' doesn't clarify when to use create_task vs create_todo (projects WITH vs WITHOUT task integration).
No error handling visible in call_tool implementation. No recovery guidance, categorization (retryable vs fatal), or actionable error messages. If an API call fails, LLM receives no direction on next steps.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 60 | 2026-07-28+ | v2 |
List all accessible projects
List all Hubstaff Tasks organization members (get Tasks-specific member IDs for create_todo)
List all Hubstaff Tasks projects (for use with get_tasks_lists and create_todo)
List all organization members to help user select personas to track
List tasks/todos in project or organization
Parameters lack constraints. 'status' enum is present in list_projects and list_tasks_projects, but date parameters (start_date, end_date) have no format validation, range limits, or examples. LLMs may pass invalid dates.
No pagination support visible. list_team_members, list_projects, list_todos, list_tasks_projects, list_tasks_members have no limit/offset/page parameters. Large result sets will blow context window.