Skip to main content
Glama
Sign In
timetree-mcp

timetree-mcp

by ap311036
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

timetree_get_occurrence_for_edit

Read-onlyIdempotent

Retrieves and validates one timed daily or weekly occurrence before editing, verifying start/end timezone alignment, DST safety, parent links, and returning revision data without calendar writes.

Instructions

Read and validate one timed DAILY/WEEKLY occurrence in Asia/Taipei, Asia/Tokyo, Asia/Kolkata, America/New_York or Europe/London. Start/end timezones must match. Returns a calendar revision and timezone; unsafe DST/metadata is rejected and unverified parent links mark it uneditable. No calendar writes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "calendar_id": "<calendar_id>",
      "event_uuid": "<event_uuid>",
      "occurrence_start_at": "<occurrence_start_at>"
    },
    "name": "timetree_get_occurrence_for_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_uuidYes
calendar_idYes
occurrence_start_atYesExact ORIGINAL local occurrence start, YYYY-MM-DDTHH:MM:SS±HH:MM. Numeric UTC offset must match the series IANA timezone; ambiguous/nonexistent local times are rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.9/5.0
Behavior5/5

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

Goes well past the annotations: discloses the return payload (calendar revision and timezone), the rejection rule for unsafe DST/metadata, and that unverified parent links render the occurrence uneditable. It also enumerates the five permitted IANA timezones, which an agent cannot get from the schema.

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?

Three dense sentences with the operation and constraints front-loaded and zero filler. It is slightly telegraphic, reading more like a spec fragment than prose.

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?

With no output schema, the description usefully characterizes the return (revision, timezone) and the uneditable outcome. It does not describe error signaling for rejected occurrences, but for a three-param read tool the essential behavior is covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, and the description compensates for occurrence_start_at by tying it to the allowed timezone list and rejection of ambiguous local times. But 'Start/end timezones must match' is confusing since the schema has only occurrence_start_at, and calendar_id/event_uuid receive no added meaning.

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 (read and validate) and resource (one timed DAILY/WEEKLY occurrence), plus the supported timezone scope. Implicitly contrasts with the mutating sibling timetree_move_occurrence via 'No calendar writes', though it never names that sibling.

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?

Establishes the read-only validation context and preconditions (matching timezones, supported timezone list), which implies this is a pre-check before an edit such as move_occurrence. However, no alternative tool is named and there is no explicit when-not-to-use statement.

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