Skip to main content
Glama
Sign In
cairn

cairn

by juw12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

capture

Create structured project notes from one line: use prefixes to classify ideas, todos, decisions, notes, or feedback, and #tags to organize them in your repo's Markdown memory.

Instructions

Create a note from one line. Prefix picks the kind: 'idea:', 'todo:', 'decision:', 'note:', 'feedback:'; #tags become tags. Example: 'decision: cache in SQLite, not Redis #storage'.

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

Input Schema

NameRequiredDescriptionDefault
bodyNoOptional Markdown body (for a decision: context, options, decision, consequences)
textYesPrefix, title and #tags on one line

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world behavior, so the safety profile is covered. The description adds the parsing behavior (prefix selects kind, #tags become tags), but says nothing about what an unrecognized prefix does, whether repeated captures duplicate, or what is returned after creation.

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 plus a single concrete example, all front-loaded with the action first and the syntax rule second. Nothing is padding; the example does real work demonstrating prefix and tag placement simultaneously.

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 two-parameter capture tool with no output schema, the description covers the input grammar well enough to call correctly. The missing piece is what happens on return (note id, confirmation) and error cases like unknown prefixes, which keeps it from being fully complete.

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, and the description earns more by documenting the prefix convention and inline #tag syntax that the schema only hints at with 'Prefix, title and #tags on one line'. It doesn't explain the interplay between text and the optional Markdown body, which is a minor remaining gap.

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?

"Create a note from one line" gives a specific verb and resource, and the prefix vocabulary ('idea:', 'todo:', 'decision:'...) makes the artifact type concrete. It doesn't explicitly contrast itself with siblings like update_note or queue_add, but a create-note verb is hard to confuse with list_notes/search/read_note.

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 conveyed only through the example ('decision: cache in SQLite, not Redis #storage'), which implies when a decision-type note is appropriate. There is no statement of when to prefer this over update_note, queue_add, or log, and no exclusion or prerequisite guidance.

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