Muninn (munn.is)

muninn_artifact_list

Read-onlyIdempotent

List stored artifacts, newest first, optionally narrowed to one format or one handle. Returns slim rows {artifactId, format, title, handle, createdAt, url, published, publicUrl, expiresAt?} — no source bodies, so it is cheap to call before deciding what to fetch. Backed by a D1 index, never a KV scan. Use this to see what you have already made for this user, or to answer 'what have I shared publicly' — every published artifact carries its live public link, and its expiresAt when it has one. A link past its expiry is reported as published: false, expired: true. To edit any row, pass its artifactId as memoryId to muninn_memory_update — there is no muninn_artifact_update. Also returns handles, every handle the account can use, so you know the valid values for handle on muninn_artifact_add and muninn_artifact_move.

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

Input Schema

Name	Required	Description
`limit`	No	Maximum rows to return.
`format`	No	Restrict to one format, e.g. 'mermaid'.
`handle`	No	Restrict to artifacts under one of the user's handles, e.g. 'chai'. Must be a handle this account holds.
`publishedOnly`	No	Return only artifacts that are currently shared publicly. Use this to answer 'what of mine is publicly reachable'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnly/destructive/idempotent, but the description adds substantial behavior beyond them: backed by a D1 index rather than a KV scan, returns slim rows without source bodies, and reports expired links as published:false, expired:true. It also discloses that it returns a `handles` list, which is non-obvious side output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but front-loads the core capability, then layers return shape, performance rationale, use cases, and cross-tool routing with no filler. Every sentence carries distinct information an agent needs.

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 fully specifies the returned row fields, the optional expiresAt, the derived expired state, and the extra `handles` collection. Nothing an agent needs to call or interpret this tool is missing.

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%, so the baseline is 3, but the description adds meaning beyond the schema by explaining that the returned `handles` array supplies the valid values for the `handle` parameter and that a link past expiry surfaces as published:false/expired:true. This goes past restating schema text.

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 (List) and resource (stored artifacts) with ordering (newest first) and scope (optionally one format or one handle). It also implicitly distinguishes itself from muninn_artifact_get by noting it is 'cheap to call before deciding what to fetch' since it returns no source bodies.

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?

Explicit when-to-use cases are given: 'see what you have already made for this user' and 'answer what have I shared publicly.' It also routes editing away from a non-existent sibling by stating 'To edit any row, pass its artifactId as memoryId to muninn_memory_update — there is no muninn_artifact_update.'

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?