Skip to main content
Glama

muninn_mirror_connect

Start the connection flow for a mirror provider. Returns a URL for the user to open in their browser. After approving, call muninn_mirror_status to confirm. Paid plan. provider: 'gdrive' (Google Drive, push-only: copies out of Muninn, never back).

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": {
      "provider": "<provider>"
    },
    "name": "muninn_mirror_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerYesThe mirror provider to connect: 'gdrive' for Google Drive (push-only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / provider / description
      Previous value: -"The mirror provider to connect: 'gdrive' for Google Drive (push-only). 'github' is not available yet and returns an error."New value: +"The mirror provider to connect: 'gdrive' for Google Drive (push-only)."
    • changedInput schema / properties / provider / enum
      Previous value: -[
      -  "github",
      -  "gdrive"
      -]New value: +[
      +  "gdrive"
      +]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare non-read-only, open-world, non-idempotent, non-destructive, so the safety profile is covered. The description adds real behavior beyond that: an out-of-band browser approval by the user, a URL return value, a paid-plan gate, and the push-only directionality ('copies out of Muninn, never back'). It does not say whether repeated calls spawn duplicate flows, though idempotentHint=false already signals that.

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?

Short sentences, front-loaded with the action and return value, then sequencing, then the constraint. The trailing provider parenthetical partially restates the schema's enum description, but it carries the directional semantics, so the redundancy earns its place.

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 one-parameter, no-output-schema tool, the definition covers the action, the return value, the required follow-up, and the plan gate. Minor omissions like URL expiry or what happens if the user abandons the flow are not enough to leave an agent unable to call it correctly.

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% with an enum on provider, so the baseline is 3. The description adds meaning beyond the schema by unpacking what 'push-only' means for Google Drive — copies leave Muninn and never come back — which shapes how the agent explains the provider choice to the user.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Start the connection flow for a mirror provider') and notes the immediate return value (a URL), so the agent knows this is an OAuth-style handoff, not a data operation. It does not explicitly contrast with the sibling muninn_artifact_connect, so the mirror-vs-artifact distinction is only implied by the word 'mirror'.

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 a clear prerequisite ('Paid plan') and an explicit follow-up step ('After approving, call muninn_mirror_status to confirm'), which tells the agent how to sequence the flow. It stops short of stating when not to call it (e.g., when a mirror is already connected), but the sequencing guidance is concrete.

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