Skip to main content
Glama
Sign In
timetree-worklog-mcp

timetree-worklog-mcp

by gideon211
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get work-log sync status

get_sync_status
Read-onlyIdempotent

Read local synchronization state, counts, attempt history, and provider health to monitor worklog sync progress and diagnose issues without writing data or calling TimeTree.

Instructions

Read local synchronization state, counts, attempt history and provider health. Without a worklogId or date it returns an aggregate summary. It never writes and does not call TimeTree.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_sync_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoCalendar date in YYYY-MM-DD form. Never infer a date the user did not provide.
timezoneNoIANA time zone, for example Africa/Accra or Europe/London
worklogIdNo

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description adds real context by stating it does not call the TimeTree provider, meaning stale provider data will not be refreshed. The default aggregate-summary behavior is also disclosed.

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?

Three short sentences, front-loaded with the resource and its returned data, followed by default behavior and the no-side-effect guarantee. Nothing is padded.

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?

An output schema exists, so return shape need not be explained, and the annotations carry the safety profile. The remaining gap is minor: it does not clarify when to escalate to retry_pending_sync if the status shows pending attempts.

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?

Schema coverage is 67% and documents date and timezone, but worklogId has no schema description. The description compensates by explaining the parameter combination semantics: no worklogId and no date collapses to an aggregate result. It could still clarify what worklogId refers to.

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?

States a specific verb and resource (read local sync state) and enumerates the returned facets: counts, attempt history, provider health. 'It never writes and does not call TimeTree' implicitly separates it from retry_pending_sync, though the sibling is never named.

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

Usage Guidelines3/5

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

'Without a worklogId or date it returns an aggregate summary' tells the agent what each calling mode yields, which implies when to pass filters. However, there is no explicit guidance on when to use this versus retry_pending_sync or get_daily_worklog, leaving the comparison to inference.

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