Skip to main content
Glama

myco_germinate

Bootstraps a new Myco substrate: creates _canon.yaml, MYCO.md, and .myco/state/autoseeded.txt. For initial project setup only.

Instructions

Bootstrap a new Myco substrate: creates _canon.yaml (contract + identity + subsystems), MYCO.md (or the named entry-point), and .myco/state/autoseeded.txt at the target project directory. Call this once per project — for every subsequent action, other verbs take over and this one raises "substrate already exists".

Use this when: starting a brand-new substrate for a project that does not yet have _canon.yaml. Do NOT use this when: the project already has a substrate (pulse reports substrate_id), when the workspace has _canon.yaml in a parent directory (you are already inside a substrate), or when you only want to ingest into an existing substrate (use myco_eat instead).

Side effects: writes 3 files (see germination doctrine for the exact canon shape); registers the substrate in ~/.myco/substrates.yaml so myco graft --list-substrates finds it. Honors R6 write_surface (the freshly-stamped canon includes notes/, docs/, src/, .myco/ by default).

Returns: { exit_code, files_created, preview, dry_run, project_dir, substrate_id }. The preview dict shows the first line and byte count of each written file; dry_run=true returns the same shape without writing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_dirYesAbsolute or relative path of the directory that will host the new substrate. Must exist and be writable; the _canon.yaml will be created inside this directory (not a subdirectory). Use forward slashes or escaped backslashes on Windows.
substrate_idYesStable slug identifying this substrate across the mycelial network. Used in cross-substrate propagation + the ~/.myco/substrates.yaml registry. Recommend kebab-case, human-readable (e.g. 'neurips-2026-research' or 'my-company-infra'). No uniqueness check; reuse silently overwrites registry entries.
tagsNoFree-form affiliation tags attached to the substrate identity (e.g. ['research','production','personal']). Per L0: tags are NOT boundaries — they don't gate writes, they only describe. Stored at _canon.yaml::identity.tags and surfaced in substrate_pulse for grep-friendly discovery.
entry_pointNoFilename of the agent-entry markdown that the substrate opens with. Defaults to MYCO.md (Myco-native convention). Override to 'CLAUDE.md' when you want the substrate to share an entry with Claude-ecosystem conventions. The file gets created if absent; existing files are not overwritten unless --force.MYCO.md
dry_runNoWhen true, compute the files that would be written + return their byte count and first line in the preview payload, but do NOT touch disk. Use for 'what would happen if I germinate here' inspection without committing. Default false (writes immediately).
Behavior5/5

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

With no annotations provided, the description fully discloses side effects: writes 3 files, registers in substrates.yaml, honors R6 write_surface. It also states that subsequent calls raise 'substrate already exists' and explains the return value including preview and dry_run behavior.

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 a purpose paragraph, usage guidelines, side effects, and return shape. It is front-loaded with the essential purpose, but is somewhat long. However, every sentence adds value, making it appropriate for the tool's complexity.

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?

Without an output schema, the description provides detailed return shape including exit_code, files_created, preview, dry_run, project_dir, substrate_id. It covers preconditions, error states, and all behavioral aspects, leaving no gaps for an AI agent.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant context beyond schema: explains that project_dir must exist and be writable, substrate_id is for cross-substrate propagation, tags are not boundaries per L0, entry_point defaults to MYCO.md with override option, and dry_run computes without writing.

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 clearly states 'Bootstrap a new Myco substrate' and enumerates the files created (_canon.yaml, MYCO.md, .myco/state/autoseeded.txt). It distinguishes from siblings by noting that other verbs take over after initial creation and explicitly mentions myco_eat for existing substrates.

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 includes a dedicated 'Use this when' and 'Do NOT use this when' section, with clear preconditions (no _canon.yaml, no parent substrate) and a specific sibling alternative (myco_eat). This provides explicit guidance for when to invoke the tool.

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/Battam1111/Myco'

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