Skip to main content
Glama
Sign In
cairn

cairn

by juw12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

log

Adds a timestamped line to today's journal page, and lines starting with todo:, idea:, or decision: also create and link the matching note.

Instructions

Add a timestamped line to today's journal page. 'todo:'/'idea:'/'decision:' lines also create that note and link it.

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": {
      "text": "<text>"
    },
    "name": "log"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare a non-destructive, non-idempotent write. The description goes beyond them by disclosing a conditional side effect: lines prefixed with 'todo:', 'idea:', or 'decision:' create and link a note. It does not say whether the prefix list is exhaustive or what the note is titled, but the main hidden mutation is surfaced.

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?

Two short sentences with no padding; the primary action is front-loaded and the conditional side effect follows immediately after.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter write tool with no output schema, the core action and side effect are covered. Gaps remain around what is returned (the created note? the line?), whether the prefix set is closed, and whether appended lines are deduplicated given non-idempotency.

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 0% for the single 'text' parameter, so the description must carry the meaning — and it does partially by explaining prefix-based interpretation of the text. It does not cover formatting limits, multiline input, or whether the timestamp is auto-generated and unauthorable.

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 target: 'Add a timestamped line to today's journal page.' That distinguishes it from note-reading/searching siblings, though it does not explicitly contrast with 'capture' or 'precedent_log', which may overlap. The side-effect clause adds precision about what gets created.

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?

Usage is implied by the fixed target (today's journal page), so an agent can infer this is the quick-daily-logging path. There is no explicit when-to-use/when-not guidance or named alternative such as 'capture' or 'update_note' for other destinations.

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