Skip to main content
Glama

myco_intake

Bulk-ingest an entire directory tree of documents into the substrate, creating notes for each file. Supports regex selection, ingest cap, and dry-run preview.

Instructions

Walk a directory, list every adapter-ingestible file via myco_forage, then call myco_eat on each. The atomic bulk-ingest composer that replaces the v0.5.x unimplemented forage --digest-on-read flag.

Single-responsibility composition: forage stays read-only; eat stays single-note; intake is the only verb that composes both with a write side-effect.

Use this when: a fresh substrate needs to absorb an existing directory tree (a paper archive, a code repository, a meeting-log folder). Use --filter regex to select a subset; --max to cap ingest count; --dry-run to preview.

Failure semantics: per-file ingest failures produce a status: failed stub note in notes/raw/ (NOT silent skip; see L0 P2 + AD1 dim) and are reported in the result payload's failures list. --strict mode raises on any failure (exit_code=2).

Side effects: writes 0+ notes to notes/raw/ (one per ingestible file, with frontmatter status=ok|failed). R6 write_surface gated.

Returns: { exit_code, ingested, failed, failures, notes, dry_run }. Use myco_assimilate afterwards to promote the successful raws to integrated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute or substrate-relative directory path to scan recursively. Forwarded to myco_forage to list adapter-handled files; each gets ingested via myco_eat. Use forward slashes or escaped backslashes on Windows.
filterNoOptional regex applied to the candidate path string. Only files whose path matches are ingested. Useful for slicing a large tree (e.g. only PDFs: ``\.pdf$``; only one subdir: ``^docs/research/``).
maxNoHard cap on number of files ingested. Useful for staged ingest of a very large directory: run with --max=100 first, assimilate, then re-run.
dry_runNoWhen true, list intended ingest actions without writing. The payload's ``ingested`` and ``notes`` reflect what WOULD happen.
strictNoWhen true, any per-file ingest failure raises MycoError (exit_code=2) — strict-mode treats partial failure as full failure. Default false: failures produce stub notes and continue.
project_dirNoAbsolute path of the workspace / project whose Myco substrate this call targets. Overrides auto-discovery. When omitted, Myco resolves via MCP roots/list, then MYCO_PROJECT_DIR, then cwd — the substrate_pulse field in every response echoes which source answered.
Behavior5/5

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

No annotations are provided, but the description fully discloses side effects (writes to notes/raw/), failure semantics (stub notes, failures list, --strict mode), return payload structure, and access control ('R6 write_surface gated'), exceeding the burden.

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 fairly long but well-structured with clear paragraphs and bullet points. It front-loads the core action and every sentence adds value, though minor trimming could improve conciseness.

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?

Despite no output schema, the description explains the return payload ({ exit_code, ingested, failed, failures, notes, dry_run }) and mentions subsequent myco_assimilate. It covers all 6 parameters, side effects, failure handling, and usage context, making it fully complete for an 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?

Although schema coverage is 100%, the description adds substantial context for each parameter: path is forwarded to myco_forage, filter uses regex, max for staged ingest, dry_run preview, strict failure mode, and project_dir resolution order, going beyond the schema's descriptions.

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 the tool walks a directory, lists ingestible files via myco_forage, then calls myco_eat on each, explicitly distinguishing it from siblings by noting that forage stays read-only and eat stays single-note.

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

Usage Guidelines4/5

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

The description explicitly states when to use: 'when a fresh substrate needs to absorb an existing directory tree' and provides guidance on options like --filter, --max, --dry-run. It contrasts with sibling tools but does not explicitly state when not to use this 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