Skip to main content
Glama
Sign In
selfos-mcp

selfos-mcp

by AmineBenaceur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_note

Append a fact you told the assistant to a vault note, auto-creating the file if needed. Use it to record preferences, people details, or journal entries in one subject per file.

Instructions

Append a fact the user told you to a vault file (one subject per file), e.g. 'people/jane-doe.md', 'profile/preferences.md', 'journal/2026-10-16.md' (auto-created). Pass create to make a new person/area file.

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

Input Schema

NameRequiredDescriptionDefault
pathYes
textYes
createNo
sectionNoHeading to append under, e.g. 'Communication'
inferredNoTrue only for your own conclusion, not something the user said

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already tell the agent this is a non-read-only, non-destructive, closed-world operation. The description adds genuinely useful traits beyond that: appends rather than overwrites, files are auto-created, and one subject per file. It is silent on what happens for a missing path without `create` and on any return value.

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 front-loaded sentences: the core append behavior first, then the `create` escape hatch. Dense but every clause carries information; the example paths could be trimmed but they earn their place by defining the path convention.

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 5-parameter mutation tool with a nested object and no output schema, the description covers the essentials — what is written, where, and how new files get created. Remaining gaps (missing-path behavior, section/inferred semantics) are real but secondary to calling it correctly.

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 only 40%, but the description compensates partly by explaining the path format with three examples and the meaning of `create`. It says nothing about `section`, `inferred`, or the nested create fields (title/aliases/relationship), leaving those to sparse schema text.

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 resource — 'Append a fact ... to a vault file' — plus the one-subject-per-file convention and concrete path examples, which clearly separates it from read-oriented siblings like read_file and search. It doesn't explicitly contrast with update-style siblings, but the append semantics are unambiguous.

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?

Implies usage ('a fact the user told you to', 'Pass `create` to make a new person/area file') but never states when not to use it, nor how it relates to read_file or other vault tools. The `create` condition is the only explicit branch 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