Skip to main content
Glama

knowledge_commit

Save a dated Markdown note about a session or decision, either in a project's Notes folder or the shared Notes folder.

Instructions

Сохранить заметку о сессии/решении. Кладёт новый файл в Projects/<проект>/Notes/ или в Notes/ с датой в имени.

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": {
      "title": "<title>",
      "body": "<body>"
    },
    "name": "knowledge_commit"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
titleYes
projectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the meaningful behavior of where the file lands and that a new file is created with the date in the name. It does not say what happens on name collision (overwrite vs. duplicate), whether the project directory is auto-created, or what the call returns.

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?

Two short sentences, front-loaded with the action before the storage detail, with no filler. Slightly under-specified rather than padded, which is the better failure mode.

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

Completeness2/5

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

A 3-parameter write tool with no annotations and no output schema needs more: parameter meaning, overwrite semantics, and return behavior are all absent. The path scheme is the only piece of operational detail supplied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only indirectly explains 'project' via the path template. It says nothing about what 'title' and 'body' map to (filename stem? heading?) or what happens when 'project' is omitted, which is the entire branching logic mentioned.

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 concrete verb and resource ('Сохранить заметку о сессии/решении') and adds the destination scope (Projects/<проект>/Notes/ or Notes/). The phrase 'новый файл' implicitly separates it from knowledge_append, but no sibling is named explicitly.

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 only implied by the noun phrase 'заметку о сессии/решении' — an agent can infer this is for recording session/decision notes. There is no explicit statement of when to prefer it over knowledge_write, knowledge_append, or knowledge_commit, and no prerequisites are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.