Muninn (munn.is)

muninn_picture_upload_start

Upload photos to Muninn: shows a photo picker inside the chat so the user picks the photos there, with nothing attached first. Use whenever the user wants to upload, save, add or keep a photo or picture in Muninn (a moment, a trip, a family picture) and has NOT already attached it in this chat. Never ask the user to attach a photo instead of calling this. If the photos are already attached here and your code can read them, use muninn_picture_upload_direct instead. Returns {memoryId, uploadUrl, expiresAt, maxFiles}. In chats that show app widgets a photo picker appears with this result and posts a message for the user when they finish; tell the user to pick photos in it, and give uploadUrl as a link in case no picker appears. Up to 7 photos, JPEG, PNG or WebP, 10 MB each, for 15 minutes. Photos picked this way keep their original date and camera. When the user is done, call muninn_picture_view with memoryId, then muninn_picture_upload_finish. Nothing is a memory until finish runs.

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

Input Schema

Name	Required	Description	Default
`maxFiles`	No	How many photos this memory will hold, 1 to 7. Omit for 7.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations (which only flag it as a non-idempotent write), the description discloses the picker/widget behavior, that a message is posted for the user, the return shape {memoryId, uploadUrl, expiresAt, maxFiles}, constraints (7 photos, JPEG/PNG/WebP, 10 MB, 15 minutes), metadata preservation, and the crucial state fact that nothing becomes a memory until finish runs.

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?

The description is long but front-loads the core action and routing rule, then stacks return values, constraints, and workflow in sequence. Nearly every sentence earns its place, though the return-value and workflow details could be tightened slightly.

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?

For a tool with no output schema, the description fully covers the return object, the multi-step completion workflow, UI behavior, and hard constraints. An agent has everything needed to call it and guide the user afterward.

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?

There is only one optional parameter and the schema already documents it at 100% coverage, including the 'Omit for 7' default. The description's 'Up to 7 photos' reinforces maxFiles but adds no syntax or meaning beyond the schema, so the baseline of 3 applies.

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?

The description states a specific verb and resource (upload photos to Muninn) and explains the mechanism (in-chat photo picker). It explicitly distinguishes itself from the sibling muninn_picture_upload_direct based on whether photos are already attached.

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?

It gives explicit trigger conditions ('whenever the user wants to upload, save, add or keep a photo... and has NOT already attached it'), an explicit exclusion ('Never ask the user to attach a photo instead'), and names the alternative tool plus its selecting condition. It also spells out the surrounding workflow (view, then finish).

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?