Skip to main content
Glama

Inspect Artifact

inspect_artifact
Idempotent

Inspect an active archive or application package in one call to map its artifact graph, integrity findings, and next probes before extracting files.

Instructions

Inspect an active archive or application package in one call. By default returns the complete content-addressed artifact graph once, as the typed nested inventory Evidence, with root and integrity observations, integrity contradictions, hypotheses, unexplored branches, limitations, and next probes inline. Optional detail summary retains the complete inspection and returns its derived summary view; read exact paths or inventory pages with inspect_analysis_view using parent_evidence_id. This changes delivery, not inventory coverage. Read-only DMG mounting is used automatically on supported macOS hosts. Integrity mismatches fail by default; record-and-continue keeps mismatches explicitly untrusted. It does not extract files; use extract_artifact to materialize its regular contents.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "inspect_artifact"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoOmitted or complete returns the complete inspection Evidence. summary retains that complete Evidence in this session and returns its inspect_analysis_view summary; use normalized_result.parent_evidence_id for inventory views.
integrity_policyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Adds a lot beyond annotations: DMG mounting happens automatically only on supported macOS hosts, integrity mismatches fail by default unless record-and-continue is set, and that mode leaves mismatches explicitly untrusted. It also discloses that detail=summary retains the complete Evidence in-session. A minor tension exists with readOnlyHint=false, since the description emphasizes read-only mounting, but mounting is a host side effect, so this reads as nuance rather than contradiction.

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?

Front-loaded with the purpose and one-call scope, then alternatives, then the mount and integrity-policy behavior. Dense but every sentence carries a distinct rule. There is slight overlap with the schema's own detail description, which is acceptable.

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?

There is no output schema, so the description must explain the return value, and it does: a nested Evidence inventory with root and integrity observations, contradictions, hypotheses, unexplored branches, limitations, and next probes. That is enough for an agent to call it correctly and follow up through inspect_analysis_view.

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?

The schema describes detail at length but leaves integrity_policy bare, so the description must, and does, explain that 'fail' is the default and records mismatches as untrusted under 'record-and-continue'. It also clarifies the practical consequence of detail (retention plus parent_evidence_id for follow-up views), which is meaning beyond the enum values.

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?

Names a specific verb and resource: inspect an archive or application package, returning a content-addressed artifact graph as typed Evidence. It explicitly distinguishes itself from extract_artifact (materializes files) and inspect_analysis_view (paths and pages), so the agent can place it in the workflow without reading a schema.

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

Usage Guidelines4/5

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

Gives concrete routing: use inspect_analysis_view with parent_evidence_id for exact paths or paged inventory, and extract_artifact to materialize contents. The detail=summary case is described as a delivery-mode choice rather than a coverage change. Missing only an explicit statement of when this tool is the wrong choice among the many sibling archive inspectors.

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

Deploy Server

Other Tools