Skip to main content
Glama
markwharton

Time Tracking MCP

by markwharton
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Time Tracking MCP

No user-submitted related servers found.

    Related Servers

      Deploy Server
      Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

      TDQS

      A3.8/5.0

      Scored across 1 tool

      Disambiguation5/5

      With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'log_time' has a clear, distinct purpose of recording time entries, so agents cannot misselect between non-existent alternatives.

      Naming Consistency5/5

      The naming pattern cannot be inconsistent with only one tool. The tool name 'log_time' follows a clear verb_noun convention that would be appropriate if more tools were added, but with a single tool, consistency is inherently perfect.

      Tool Count2/5

      A single tool is insufficient for a time tracking domain that typically requires operations like listing, editing, deleting, or reporting on time entries. While the tool itself is well-described, the server's scope feels incomplete with only creation/logging functionality, lacking basic CRUD coverage.

      Completeness2/5

      The tool set is severely incomplete for time tracking. There is no way to retrieve, update, delete, or analyze logged time entries—only creation via 'log_time'. This creates dead ends for agents that need to review or modify existing data, significantly limiting practical utility.

      Resources