Gnosys

gnosys_init

Destructive

Initializes a new project root by creating .gnosys metadata and registering it in the central SQLite store, returning identity, store path, and setup summary. Run before project-scoped operations.

Instructions

Initialize a project directory, returning its identity, store path, and setup summary. Pass an absolute directory (e.g. /work/app); projectName defaults to its basename. Creates .gnosys/ metadata and registers the project in the central SQLite store; run this before project-scoped operations on a new root. Use gnosys_briefing instead to inspect an already registered project.

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": {
      "directory": "<directory>"
    },
    "name": "gnosys_init"
  }
}

Input Schema

Name	Required	Description
`directory`	Yes	Absolute path to the project directory to initialize. Required.
`projectName`	No	Human-readable project name. Defaults to directory basename.
`projectRoot`	No	Project root path; routes the call to that project's store.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv7.0.0Oct 21, 2026

TDQS

A4.1/5.0

Behavior3/5

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

The description discloses side effects the annotations don't spell out: it creates .gnosys/ metadata and writes a registration into the central SQLite store, which explains the openWorldHint. But annotations declare destructiveHint=true and idempotentHint=false, and the description never says what happens on re-initialization of an existing root or what could be overwritten — the key risk an agent needs to know.

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?

Three tight sentences that front-load purpose then prerequisites then the alternative. The return-value clause and the absolute-path example are both useful, though the example is arguably redundant with the schema.

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?

No output schema exists, and the description does say what comes back, plus the setup prerequisite and the sibling route. The remaining gap is re-initialization semantics, which matters given destructiveHint=true.

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%, so the baseline applies. The description reinforces the absolute-path requirement with an example and restates the projectName default, but it adds nothing about projectRoot, the one parameter whose routing behavior ('routes the call to that project's store') is the least obvious.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Initialize a project directory') and immediately names what it returns (identity, store path, setup summary). It also separates itself from the sibling gnosys_briefing, which inspects an existing project rather than creating one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ('run this before project-scoped operations on a new root') and an explicit alternative with its condition ('Use gnosys_briefing instead to inspect an already registered project'). Little is left to inference.

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

Deploy Server