Skip to main content
Glama

myco_hunger

Compose a structured hunger report for Myco substrate: detect contract drift, note backlog, reflex signals, and advise next actions. Use as first call each session or mid-session refresh.

Instructions

Compose the substrate's hunger report: contract drift (canon version mismatch), raw-note backlog (integer count of notes/raw/*.md pending assimilation), active reflex signals (HIGH/MEDIUM/LOW), concrete next-action advice, and per-kind count of substrate-local plugins. This is the R1 BOOT RITUAL — the mandatory first substantive action every session per the Hard Contract.

Use this: as the FIRST tool call of every session without exception (R1 is a contract rule, not a suggestion). Use it again mid-session whenever the agent wants a fresh state snapshot — it's cheap and idempotent. Do NOT use it as a substitute for myco_brief (which is human-facing markdown, this is agent-facing structured data).

Side effects: none by default. When execute=true, patches <entry_point>'s <!-- MYCO-BOOT-SIGNALS:BEGIN ... END --> block with the current hunger signals, respecting R6 write_surface. On abrupt exit (~1.5s kill budget, SessionEnd hook) prefer myco_senesce with quick=true; hunger itself does not auto-trigger senesce.

Returns: { exit_code, report: { contract_drift, raw_backlog, reflex_signals, advice, local_plugins: { count, count_by_kind, errors, overlay_verbs } }, execute, entry_point_patched }. The substrate_pulse sidecar then tells you which rule to honor next (advances from R1 → R3 after first hunger call).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
executeNoWhen true, write the boot_brief.md + patch the entry-point's MYCO-BOOT-SIGNALS block with current reflex signals. When false (default), compute the report but make zero writes — useful for 'peek without touching'. R6 write_surface still applies to the patched entry-point path.
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?

Describes side effects: none by default, but when execute=true writes to entry-point. Mentions behavior on abrupt exit (~1.5s kill budget) and that hunger does not auto-trigger senesce. With no annotations, the description fully discloses 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?

Description is somewhat lengthy but each sentence adds essential information. Could be slightly more concise, but structure is logical and front-loads the purpose.

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 two parameters with full schema coverage and no output schema, the description details return fields (exit_code, report with subfields) and mentions the substrate_pulse sidecar. Provides sufficient context for correct tool usage.

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. Description adds value by explaining the effect of execute (peek vs. write) and project_dir resolution order. Exceeds baseline.

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 composes a hunger report with specific components (contract drift, raw-note backlog, reflex signals, advice, plugin counts). It distinguishes itself from myco_brief by noting the tool provides agent-facing structured data versus human-facing markdown.

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?

Explicitly states this is the mandatory first tool call every session per the Hard Contract (R1 BOOT RITUAL). Also advises using it mid-session for fresh state snapshots, and specifies not to use it as a substitute for myco_brief. Clear when to use and when not.

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