Skip to main content
Glama

knotlog_note

Append one line to today's session reflection note in the Knotlog vault; adds only that line and writes nothing else.

Instructions

Append one line to today's session reflection note in the Knotlog vault (append-only, the same as knotlog note); writes nothing else.

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

Input Schema

NameRequiredDescriptionDefault
textYesOne line to add

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses append-only semantics and 'writes nothing else', which tells the agent this is a narrow, non-destructive-to-existing-content mutation. It leaves open whether the note is created if absent and what the call returns, but the core write behavior is clear.

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?

One sentence, front-loaded with the verb and target, and the trailing 'writes nothing else' earns its place by constraining behavior. The parenthetical comparison to another tool is slightly wasteful since that tool is not a listed sibling.

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 one-parameter append tool with no output schema and no annotations, the definition covers what is needed to invoke it correctly. Missing details are minor: what happens on a fresh vault, and whether the text is truncated or newline-normalized.

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?

There is a single required parameter with 100% schema description coverage ('One line to add'), so the schema already does the work and the baseline of 3 applies. The description reinforces the one-line constraint but adds no format, length, or escaping guidance.

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 gives a specific verb and target: append one line to today's session reflection note in the Knotlog vault. That is concrete and distinguishable from the read-oriented siblings (knotlog_context, knotlog_search), though it never explicitly names them as alternatives.

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 rather than stated: writing a reflection line for the current session. There are no explicit when-to-use/when-not-to-use rules, and the reference to 'the same as knotlog note' points at a tool that is not among the listed siblings, which could confuse an agent rather than route it.

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