Muninn (munn.is)

muninn_mirror_designate

Idempotent

Designate (or un-designate) a bundle for mirroring to a provider. Adds/removes the 'gdrive-mirror' tag on the bundle root's backing memory for Drive ('github-mirror' for GitHub). After designating, writes to that bundle automatically enqueue a mirror push. Use muninn_mirror_push to force one now. Turning mirroring on is Paid plan; turning it off (enabled=false) is always free. GitHub is not available yet: enabling it is refused, un-designating still works.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rootKey": "<rootKey>",
      "provider": "<provider>"
    },
    "name": "muninn_mirror_designate"
  }
}

Input Schema

Name	Required	Description
`enabled`	No	true = designate; false = stop mirroring this bundle
`rootKey`	Yes	node_key of the bundle root to designate
`provider`	Yes	Which provider to designate for: 'gdrive'. 'github' is accepted only with enabled=false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, idempotent, openWorld): it discloses the tag side effect on the backing memory, the automatic enqueue-on-write behavior after designation, billing implications, and a provider-specific refusal path. These are operationally critical traits annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five tight sentences, front-loaded with the core action and mechanism, followed by behavior, billing, and provider caveats. Every sentence carries non-redundant information.

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?

With no output schema, the description covers everything an agent needs: what changes, what happens afterward, cost/policy gating, provider limitations, and the force-push alternative. No material gap remains.

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 the baseline is 3, but the description adds useful semantics: enabled=false means stop mirroring and is free, and the github provider value is only usable with enabled=false. It does not elaborate on rootKey beyond the schema wording.

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?

States a specific verb and resource — designating/un-designating a bundle for mirroring to a provider — and clarifies the concrete mechanism (tagging the bundle root's backing memory). It is clearly distinguishable from sibling mirror tools (push, connect, status, reconcile).

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 routes the agent to muninn_mirror_push for forcing a push now, states the Paid-plan gate for enabling versus the always-free disable path, and warns that GitHub enabling is refused while un-designating still works. When-to-use, when-not, and the alternative are all present.

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

All Muninn (munn.is) tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?