Skip to main content
Glama

muninn_mirror_status

Read-onlyIdempotent

Report mirror connection state and push health per provider. Shows connected, last push time, pending count, and last error. Free on every plan. Covers Google Drive. On a lapsed (non-Paid) account pushes are paused, so pending can grow until it pays again.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "muninn_mirror_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerNoWhich provider to check: 'gdrive' (Google Drive). Omit for the same.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / provider / description
      Previous value: -"Which provider to check: 'gdrive' or 'github' (reported, but not a working mirror yet). Omit for all."New value: +"Which provider to check: 'gdrive' (Google Drive). Omit for the same."
    • changedInput schema / properties / provider / enum
      Previous value: -[
      -  "github",
      -  "gdrive"
      -]New value: +[
      +  "gdrive"
      +]
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description goes beyond that with genuinely non-obvious context: it is free on every plan, it currently covers only Google Drive, and pushes are paused on a lapsed non-Paid account so pending can accumulate. That billing/lifecycle detail is exactly the kind of thing annotations cannot carry.

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?

Four short sentences, front-loaded with the core purpose and returned fields before the plan/quota caveat. Minor waste: 'per provider' plus 'Covers Google Drive' partly restate the parameter, and 'until it pays again' is informal, but nothing is genuinely extraneous.

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?

With no output schema, the description usefully names the returned values (connected, last push time, pending count, last error), which is the main gap it needed to close. For a one-parameter read-only tool this is close to complete; only explicit sibling routing is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single 'provider' parameter already has an enum and description, so the schema does the work. The description's 'Covers Google Drive' corroborates the enum value but adds no syntax, default, or omission behavior beyond what the schema states. Baseline 3 applies.

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?

The first sentence gives a specific verb and resource ('Report mirror connection state and push health per provider'), and the next sentence enumerates exactly what is reported. It is clearly a read/status tool distinct from mutating siblings like muninn_mirror_push or muninn_mirror_connect, though it never names those alternatives explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Guidance is implied rather than stated: the description explains the lapsed-account condition under which 'pending can grow', which hints at when this diagnostic matters. There is no explicit 'use this when you want X; use muninn_mirror_push/reconcile when Y' routing, so the agent must infer the split from sibling names.

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