Skip to main content
Glama

init

Returns the Nogra init bundle for Claude Code to write workspace files locally. Use to initialize a Nogra workspace after MCP server setup.

Instructions

Return the public Nogra init bundle for Claude Code to write locally.

    This tool is the server-side source for Nogra workspace files. It does not write files and does not
    execute commands. The caller's Claude Code client should write each returned file into the user's chosen
    workspace path using the file writePolicy. Newer clients should use the returned installPlan
    for phase-grouped writes and a quieter installation summary.

    When to use:
    - Initialize Nogra in a customer workspace after the hosted MCP server has been added.
    - Respond to user requests such as "run Nogra init" or "/nogra init".
    - Retrieve the current public-safe Nogra workspace methodology bundle.
    - Use mode=plugin when the Nogra plugin is installed; plugin mode returns only workspace bootstrap files,
      not plugin-owned commands or skills.

    When NOT to use:
    - Do not treat this as an installer that can write to the user's filesystem.
    - Do not overwrite files marked ask_before_overwrite without asking the user.
    - Do not expect this to configure provider auth, run local commands, or perform workspace execution.

    Examples:
    >>> init(workspace_name="Acme App")
    {"schema": "nogra.init.bundle.v1", "releaseVersion": "v1.0.0", "status": "ready", "writeMode": "client_writes_files", "files": [...]}
    >>> init(workspace_name="Acme App", mode="plugin")
    {"schema": "nogra.init.bundle.v1", "releaseVersion": "v1.0.0", "initMode": "plugin", "files": [...]}
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoInit bundle mode. Use standalone for MCP-only installs; use plugin when the Nogra plugin already provides commands, skills and MCP configuration.standalone
workspace_nameNoOptional local workspace display name. Empty uses local. The user may ask for this as 'run Nogra init' or '/nogra init'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

The description clearly states that the tool does not write files and does not execute commands, and explains its server-side role. Since no annotations are provided, the description fully covers behavioral traits.

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?

The description is well-structured with clear sections and examples, but it is somewhat lengthy. However, every sentence adds value, so it earns a 4.

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

Completeness5/5

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

Given the tool has 2 parameters with full schema coverage and an output schema, the description is complete. It covers purpose, usage, parameters, examples, and behavioral constraints.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds context by explaining default values and mode semantics (plugin vs standalone) with examples, but the schema already defines these well.

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?

The description specifies the verb 'Return' and resource 'public Nogra init bundle', clearly distinguishing it from file-writing or execution tools. It explicitly states what the tool does: provide a bundle for Claude Code to write locally.

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?

The description gives explicit when-to-use scenarios (initialize Nogra, respond to user requests, retrieve bundle) and when-not-to-use (not an installer, not overwrite without asking, not configure auth/run commands). It also differentiates mode=plugin vs standalone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nograai/nogra-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server