Skip to main content
Glama

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. 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.

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

NameRequiredDescriptionDefault
enabledNotrue = designate; false = stop mirroring this bundle
rootKeyYesnode_key of the bundle root to designate
providerYesWhich provider to designate for: 'gdrive' (Google Drive).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / provider / description
      Previous value: -"Which provider to designate for: 'gdrive'. 'github' is accepted only with enabled=false."New value: +"Which provider to designate for: 'gdrive' (Google Drive)."
    • changedInput schema / properties / provider / enum
      Previous value: -[
      -  "github",
      -  "gdrive"
      -]New value: +[
      +  "gdrive"
      +]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (which only declare mutating, idempotent, non-destructive, open-world) by disclosing the concrete mechanism (adds/removes a 'gdrive-mirror' tag on the bundle root's backing memory), the automatic side effect (subsequent writes enqueue a mirror push), and the plan/pricing asymmetry between enabling (Paid) and disabling (free).

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?

Four tight sentences, front-loaded with the core action, then mechanism, then side effect, then cost. No filler and no repetition of the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter mutation tool with no output schema, the description covers behavior, side effects and pricing well. The remaining gap is the lack of stated prerequisites (e.g., whether muninn_mirror_connect must run first and what happens if the provider isn't linked).

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; the description adds real meaning by tying enabled=false to the free un-designate path and framing the tool as a toggle rather than a one-way action. It adds little for rootKey and provider beyond what the schema already documents.

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 (designate/un-designate) and resource (a bundle for mirroring to a provider), and immediately distinguishes itself from muninn_mirror_push, which is named as the tool for forcing a push instead. An agent can tell exactly what this tool changes without opening the schema.

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?

Gives clear context for use: call it to turn mirroring on or off, and redirects to muninn_mirror_push when a push should happen immediately. It does not mention prerequisites such as whether a provider must already be connected via muninn_mirror_connect, nor when to prefer muninn_mirror_status or muninn_mirror_reconcile.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources