Skip to main content
Glama
Sign In
selfos-mcp

selfos-mcp

by AmineBenaceur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

init_vault

Creates the local plain-text vault from a template when it does not exist yet, optionally initializing it as its own git repository for version control.

Instructions

Create the vault from the template if it doesn't exist yet.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "init_vault"
  }
}

Input Schema

NameRequiredDescriptionDefault
gitNoMake the vault its own git repo

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 declare readOnlyHint=false and destructiveHint=false, so safety is covered by structured data. The description adds real value by disclosing the existence check, telling an agent the call is idempotent and non-destructive to an existing vault. It does not say what happens when the vault already exists (silent no-op vs. error) or where the vault is created.

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?

One sentence, front-loaded with the action, with the conditional guard placed where it matters. Nothing is wasted and nothing is buried.

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 one-optional-param tool with annotations and no output schema, the description is nearly sufficient. But it leaves the agent guessing about the post-condition when the vault already exists and about where the vault lives, which matters for a setup tool that may be called repeatedly.

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 100% for the single optional 'git' boolean, which is already self-documenting ('Make the vault its own git repo'). The description adds no meaning about the parameter or its default, so baseline 3 applies.

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 (create the vault) plus a source (from the template) and an idempotency condition. No sibling tool in the list creates or initializes anything, so it is distinguishable, though the description never clarifies what a 'vault' or 'template' is in this product.

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?

The clause 'if it doesn't exist yet' implies this is a bootstrap/setup step that is safe to call defensively, which is useful guidance. However, it never states when in a workflow an agent should reach for it (first run? after failure?) and names no alternatives.

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