Skip to main content
Glama
STiFLeR7

Waypoint

by STiFLeR7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

log_watch

Idempotent

Record work done in the current session to a tracked project's Markdown ship's log, optionally updating Done and Next lines without changing status or creating files.

Instructions

Log a watch (add one log entry) to a tracked project's ship's log (Log section), for work actually done in this session, with your own tool id. Pass done/next if the work changed them: the Done and Next lines in Now and its Updated date are set in the same write. It never changes Status or Attention and never creates files. Calling it again with the same date, tool and text does nothing (Done and Next included).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoOptional local date (YYYY-MM-DD), within one day of today. Defaults to today.
doneNoOptional. The new Done line for Now (one line), if this work changed it.
nextNoOptional. The new Next line for Now (one line), if this work changed it.
toolYesYour tool id, e.g. claude-code for Claude Code, codex for Codex.
projectYesExact project name, as listed by take_fix.
summaryYes1–3 short lines on what was done. Stored as a quoted block.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • addedInput schema / properties / done
      Added value: +{
+  "description": "Optional. The new Done line for Now (one line), if this work changed it.",
+  "maxLength": 300,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / next
      Added value: +{
+  "description": "Optional. The new Next line for Now (one line), if this work changed it.",
+  "maxLength": 300,
+  "minLength": 1,
+  "type": "string"
+}
  2. First observedv0.2.0

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses concrete side effects and non-effects: the Done/Next lines and the Now 'Updated' date are set in the same write, while Status and Attention are never changed and no files are created. Idempotency is confirmed with precise keying ('same date, tool and text'), exceeding the bare idempotentHint.

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?

Front-loaded with the core action and scope, then side-effect and idempotency details. Dense but nearly every clause carries information; only the idempotency sentence partially restates the annotation.

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?

For a 6-parameter mutation tool with no output schema, the description covers action, target, side effects, non-effects, and idempotency. It does not describe error conditions or confirmation output, but no output schema exists to defer to, leaving a minor gap.

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 100%, so the baseline is 3, but the description adds real meaning: it clarifies that 'tool' should be the caller's own id and explains how the optional done/next values interact with the Now block and its Updated date. That is semantic content the schema alone does not convey.

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?

The description states a specific verb and resource: 'Log a watch (add one log entry)' to a tracked project's 'ship's log (Log section)'. It is unambiguous about what is being written. It does not explicitly differentiate itself from siblings take_fix/read_chart/status in the main text, though the project parameter references take_fix for naming.

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?

The scope is implied by 'for work actually done in this session', which tells the agent the trigger condition. However, no alternative tool is named and there is no explicit when-not guidance, so routing against the siblings is left 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