Muninn (munn.is)

muninn_app_link

Get a link to open Muninn in the browser: a one-time sign-in link to the Muninn web app and dashboard (Memory Map, tasks, tables, artifacts, settings) that logs the user in without a password. Use it when the user asks for the Muninn link, the app link, a login or sign-in link, or to open, see or log into Muninn. The link works once and expires after 10 minutes. Give it to the user as a clickable link, tell them it works once within 10 minutes, and do not save it to memory or repeat it later; if it has expired, call this tool again for a new one.

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_app_link"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare the safe/mutating profile (readOnlyHint=false, idempotentHint=false); the description adds the critical behavioral facts beyond them: single-use, 10-minute expiry, and the instruction not to persist or repeat the link. It also tells the agent how to present it (clickable) — well beyond structured fields.

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?

Front-loaded with purpose, then triggers, then behavior. The closing sentence is a multi-clause instruction list that is slightly dense but each clause (works once, 10-minute expiry, don't save/repeat, re-call if expired) carries distinct operational value.

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 and no parameters, the description fully covers what is returned (a clickable sign-in link), its lifecycle (one use, 10 minutes), and handling on expiry. An agent has everything needed to call and use 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?

Zero parameters, so there is nothing to document and the baseline of 4 applies. The schema description coverage is trivially 100% for an empty object.

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+resource ('Get a link to open Muninn in the browser') and immediately qualifies it as a one-time passwordless sign-in link to the web app/dashboard. None of the ~80 sibling tools do this, so it is unambiguously distinguishable.

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 enumerates trigger phrases ('Muninn link', 'app link', 'login or sign-in link', 'open, see or log into Muninn') and closes the loop on the alternative action when expired ('call this tool again for a new one'). Nothing is left to inference.

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?