Skip to main content
Glama

artifact_preview

Read-onlyIdempotent

Inspect an existing artifact file to view its hash, sources, and freshness; supported images are embedded directly for quick verification.

Instructions

Show an existing file with its hash, artifact sources and freshness. MCP embeds supported images directly.

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": {
      "task_id": "<task_id>",
      "path": "<path>"
    },
    "name": "artifact_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the safety profile needs no restating. The description adds genuine context that supported images are embedded in the MCP response, which affects how an agent consumes results. It does not explain what "artifact sources" or "freshness" actually resolve to, nor what happens if the path is unknown.

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?

Two short sentences, front-loaded with the core action and free of filler. The second sentence about image embedding is somewhat abrupt but earns its place by disclosing response behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, 0% schema coverage and an entirely unexplained required task_id, the definition leaves essential calling information missing. Only the returned fields are sketchy and the embedding behavior is covered; the parameter contract is not.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning and it largely fails: path is only obliquely implied by "file", and task_id is never mentioned at all. The two required parameters remain undocumented after reading the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Show an existing file with its hash, artifact sources and freshness" names a specific verb and resource and previews the returned content. It does not differentiate itself from the nearest sibling artifact_register, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The word "existing" implies the file must already be registered, which is the only hint of when to use it. There is no statement of when to prefer file_read or artifact_register, and no preconditions or exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.