Skip to main content
Glama
Sign In
cairn

cairn

by juw12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

precedent_log

Record a completed goal's delivered output and user corrections to improve future briefs; optionally mark its queue task done by path, slug, or title.

Instructions

When a goal is done: record what was delivered and any correction the user made, so the next brief learns from it. queue_path also marks that queue task done.

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": {
      "goal": "<goal>",
      "delivered": "<delivered>"
    },
    "name": "precedent_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYes
deliveredYes
correctionNo
queue_pathNoNote path (tasks/ship-v1.md), slug (ship-v1) or title

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive, non-idempotent write, and the description adds genuine value beyond them: it discloses a side effect (queue_path also marks that queue task done) and a downstream consequence (the next brief learns from it). It still does not say what happens on a duplicate entry or what is returned, which matters for a non-idempotent write.

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 sentences, both earning their place: the trigger and primary action come first, then the queue_path side effect. No filler, no restatement of the tool name.

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 4-parameter write with no output schema and sparse schema descriptions, the definition covers purpose, trigger, and one important side effect, but omits what the call returns, duplicate/overwrite behavior, and the meaning of the required goal field beyond the trigger phrase.

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 description coverage is only 25%, so the description carries most of the burden. It meaningfully explains delivered ('what was delivered'), correction ('any correction the user made'), and queue_path's side effect, but leaves goal's expected form or granularity unstated and gives no format guidance for correction.

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 (record) and resource (delivered work plus user correction) and anchors it to a trigger condition ("When a goal is done"). It is clear what the tool produces, though it never explicitly contrasts itself with the sibling precedent_brief that consumes the record.

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?

Provides a clear invocation condition: only when a goal is done. It stops short of exclusions (e.g., mid-task notes should go to log or update_note) and does not name an alternative for the 'not done yet' case, so an agent must infer that routing.

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