Skip to main content
Glama

myco_hunger

Compiles the substrate's hunger report: contract drift, raw-note backlog, reflex signals, and plugin counts. Required as the first tool call every session to initialize the agent's cognitive state.

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?

No annotations provided, so description carries full burden. It details side effects: no writes by default, with execute=true patching entry-point block. Mentions kill budget and related tool myco_senesce. Fully describes return structure including nested fields. No contradictions.

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 moderately long but well-structured with sections for purpose, usage, side effects, and return. Every sentence adds value. Could be slightly more concise, but the organization helps readability. No fluff.

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's role as a mandatory first action and the complexity of its report, the description fully covers behavior, side effects, return format, and integration with contract rules and other tools. No gaps remain for an agent to misuse it.

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?

Parameter schema coverage is 100% with good descriptions. The description adds context: clarifies execute's write behavior and project_dir's resolution order. This exceeds schema alone, justifying above baseline 3. However, the schema already explains parameters well, so a 4 is appropriate.

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 states it composes a hunger report with specific components (contract drift, raw backlog, reflex signals, advice, plugin count). It distinguishes from sibling myco_brief by noting this is agent-facing structured data vs human-facing markdown. The purpose is clear, specific, and well-differentiated.

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 instructs to use as the first tool call every session (R1 contract rule) and mid-session for fresh state snapshot. Warns against using as substitute for myco_brief. Mentions idempotency and cheapness. Provides comprehensive when-to-use and when-not-to-use guidance.

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