Skip to main content
Glama

muninn_artifact_get

Read-onlyIdempotent

Retrieve a stored artifact by ID — returns its full source plus format, title, provenance, and whether it is currently shared publicly (published + publicUrl, plus expiresAt/expired when the link has an expiry), so you can continue working on something a previous session (or a different model) produced. Show the person something they can read, not raw source: md as formatted prose, csv as a table, json pretty-printed, code in a fenced block, and mermaid, svg or html redrawn as a live artifact if you can draw one (if you cannot, say so and offer the source); then give them the url. To WRITE your edit back, pass this artifactId as memoryId to muninn_memory_update, muninn_memory_anchor_replace or muninn_memory_append — there is no muninn_artifact_update, because an artifact's artifactId IS its memoryId. If it is published, the public link refreshes automatically. The returned rev is the body's revision number (null if never indexed): hand it back as expectedRev on that write and it FAILS rather than clobbering an edit made in between — worth carrying when you fetch now and write later, unnecessary when you write straight away.

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": {
      "artifactId": "<artifactId>"
    },
    "name": "muninn_artifact_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
artifactIdYesThe artifact's memory ID (full UUID or a unique prefix).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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, and the description adds substantive context beyond them: the public link refreshes automatically when published, expiry fields appear only when a link has one, and `rev` is a body revision that fails a write when stale. The only minor gap is that it doesn't describe size or pagination limits for very large sources.

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 the core retrieve-and-return statement, then usage, rendering and write-back guidance in logical order. It is dense and long for a one-parameter read tool; the rendering instructions (mermaid/svg/html) could be trimmed without losing the essential contract.

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?

No output schema exists, and the description covers return content well (source, format, title, provenance, published, publicUrl, expiresAt, rev, rev=null when unindexed). For a single-parameter read-only tool that is close to complete; only error behavior for a bad or ambiguous ID is left unstated.

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% for the single artifactId parameter, so the baseline is 3; the description adds real meaning by asserting that an artifact's artifactId IS its memoryId and must be passed as memoryId to the write tools. That equivalence is operationally important and only weakly implied by the schema wording.

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 and resource ("Retrieve a stored artifact by ID") and enumerates exactly what comes back: source, format, title, provenance, published/publicUrl status. It is clearly distinct from sibling muninn_artifact_list (listing) and the muninn_memory_* write tools it points to.

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 when-to-use context ("continue working on something a previous session (or a different model) produced") and explicitly routes writes elsewhere, naming muninn_memory_update, muninn_memory_anchor_replace and muninn_memory_append, plus explaining why there is no muninn_artifact_update. It also specifies a presentation procedure for the agent to follow after fetching.

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