ArtifactSmith

inspect

Retrieve an artifact's manifest, files, build log, request history, and share state, optionally adding text content for PDF, DOCX, or XLSX versions.

Instructions

Manifest, files, build log, request history, and share state. Defaults to the latest done version.

include_content is optional and defaults to false. When true, the target done version adds
content with file, size_bytes, and text when that text is within the publish character cap.
PDF, DOCX, and XLSX return content.md and set primary_binary; they do not return the binary.
Over the cap, size_bytes is set and text is omitted. A store failure sets content_error to
store_read_failed. The call still requires read permission on this workspace.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`version`	No
`artifact_id`	Yes
`include_content`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 17, 2026

TDQS

A3.7/5.0

Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses the include_content defaults, per-format handling (PDF/DOCX/XLSX returning content.md and setting primary_binary), the character-cap fallback (size_bytes set, text omitted), the failure mode (content_error=store_read_failed), and the read-permission requirement. This is exactly the extra context annotations would otherwise have to supply.

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 front-loaded with what is returned before moving into parameter behavior, and each sentence carries information. It is somewhat dense in the middle section but contains no filler.

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?

For a read tool with an output schema, the description covers the non-obvious behaviors an agent needs: version defaulting, content-cap and format handling, error state, and permission prerequisites. The main gap is that artifact_id, the sole required parameter, receives no explanation anywhere.

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 0%, so the description must compensate. It fully explains include_content (default false, what true adds, edge cases) and partially explains version via the 'latest done version' default, but artifact_id is never described. Partial compensation against three undocumented parameters justifies a middling score.

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?

The description names the concrete payload the tool returns (manifest, files, build log, request history, share state) and states the default version target, so an agent knows this is an artifact-inspection read. It does not explicitly contrast itself with siblings like status or list_artifacts, which would have earned 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?

There is no when-to-use / when-not-to-use guidance and no alternative tool is named. The only contextual hint is 'Defaults to the latest done version,' which describes behavior rather than selection criteria against status, list_artifacts, or export.

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

Deploy Server