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

timetree-worklog-mcp

by gideon211
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List TimeTree calendars

list_calendars
Read-onlyIdempotent

Lists calendars available to the configured TimeTree account so you can identify the private calendar ID to configure; read-only, requires local credentials, and never writes.

Instructions

Read-only. Lists calendars available to the configured TimeTree account. Requires local credentials but never writes. Use this to find the one private calendar ID to configure; no destructive calendar operation is exposed.

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": "list_calendars"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description largely restates that ('Read-only', 'never writes', 'no destructive calendar operation'). It does add one piece of context not in structured data — that local credentials are required — but repeats the safety profile three times instead of adding richer behavior such as failure modes when no calendar is configured.

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 short sentences, front-loaded with the read-only posture and the intended use. It loses a point for redundancy — 'Read-only', 'never writes', and 'no destructive operation is exposed' express the same fact three ways.

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 values need not be described, and nothing an agent needs to invoke this parameterless read is missing. The only residual gap is what happens when credentials or calendars are absent, which the description leaves silent.

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?

The tool takes zero parameters and the description correctly says nothing about inputs, so there is no semantic gap to close. Baseline 4 applies for a no-parameter tool.

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?

Names a specific verb and resource (list calendars on the TimeTree account), which is immediately distinguishable from the worklog/sync siblings. It doesn't explicitly name a sibling or contrast with one, but the scope is unambiguous without opening the schema.

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?

'Use this to find the one private calendar ID to configure' gives a concrete trigger for calling the tool, so the agent knows why and when to reach for it. It stops short of stating when-not to use it or naming alternatives, but none of the siblings plausibly compete.

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