Muninn (munn.is)

muninn_picture_view

Read-onlyIdempotent

See the photos of a picture memory, or of an upload that has not been finished yet. Returns each photo's thumbnail as an image, plus JSON {memoryId, pictures: [{ord, mime, takenAt, camera, viewUrl, artifactRef}], viewLinksExpireAt}. takenAt and camera are read from the original photo when it carries them (photos picked through the upload page usually do; photos sent through a chat usually do not), so a takenAt here is a date with source 'photo'. viewUrl opens the full original for the user and stops working after 5 minutes, so hand it over now and never save it into a memory. To show a photo inside an HTML artifact, put its artifactRef in an (append /thumb for the 480px version): the artifact renders it for the owner, and publishing copies it, metadata stripped, so the public page shows it through links that expire within the hour. Never put viewUrl or image bytes in an artifact. Use after the user uploads, before writing the note, and whenever the user asks to see a picture memory again.

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": {
      "memoryId": "<memoryId>"
    },
    "name": "muninn_picture_view"
  }
}

Input Schema

Name	Required	Description	Default
`memoryId`	Yes	The memoryId returned by muninn_picture_upload_start or _direct, or the id of a picture memory.

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?

Annotations declare the read-only/idempotent/non-destructive profile, but the description goes well past them: viewUrl expires after 5 minutes and must not be persisted, artifactRef renders for the owner, publishing strips metadata and yields hour-long links, and takenAt/camera provenance depends on upload path. This is unusually rich operational context.

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?

Purpose and return shape are front-loaded, and most sentences carry unique operational information. It is dense and slightly long, and the artifact-publishing/expiry theme is touched twice, but little is genuinely wasted.

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, the description itself specifies the return JSON fields and adds the constraints (link expiry, artifact embedding rules) an agent needs. Nothing material for correct invocation 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 description coverage is 100% for the single memoryId parameter, and the description mostly restates its origin (upload_start/_direct or a picture memory id) rather than adding new meaning. Baseline 3 is appropriate when the schema carries the parameter documentation.

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?

Opens with a specific verb and resource: 'See the photos of a picture memory, or of an upload that has not been finished yet.' It clearly distinguishes itself from the picture_upload_* siblings by covering the post-upload/pre-finish viewing case, so an agent can route to it 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 Guidelines5/5

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

Gives explicit timing: 'Use after the user uploads, before writing the note, and whenever the user asks to see a picture memory again.' It also states prohibitions ('never save it into a memory', 'Never put viewUrl or image bytes in an artifact'), which function as when-not guidance.

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?