Skip to main content
Glama

Extract Artifact

extract_artifact

Extracts all regular files from the active archive or application package into a fresh REA-chosen temp directory, returning its location with traversal, overwrite, cleanup, and integrity safeguards.

Instructions

Extract all regular files from the active archive or application package into a fresh temporary directory chosen by REA. The result includes its location. Rejects traversal and symlink escapes, never overwrites, and verifies cleanup. Integrity mismatches fail by default; record-and-continue extracts the observed bytes and returns each mismatch as an explicitly untrusted integrity contradiction.

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": "extract_artifact"
  }
}

Input Schema

NameRequiredDescriptionDefault
integrity_policyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing concrete safeguards: traversal and symlink escapes are rejected, existing files are never overwritten, cleanup is verified, and outputs land in a fresh temp directory. It also explains the default failure mode on integrity mismatch and precisely what record-and-continue returns (observed bytes plus explicit untrusted integrity contradictions). This is consistent with readOnlyHint=false, destructiveHint=false, and non-idempotent semantics.

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?

Dense but front-loaded: destination, safeguards, then the integrity policy contrast, with no filler sentences. Terms like 'REA' and 'integrity contradiction' are somewhat opaque jargon, costing a bit of readability.

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 single optional-parameter tool with no output schema, the description covers where files land, what is returned at a high level ('the result includes its location'), safety behavior, and the failure mode. It does not clarify whether extraction is recursive or what error surface a rejection produces, leaving minor gaps.

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 0% and the enum values are undocumented in the schema, so the description carries the load — and it does, explaining that 'fail' is the default on mismatch and that 'record-and-continue' extracts observed bytes and surfaces each mismatch as an explicitly untrusted integrity contradiction. It never names the parameter 'integrity_policy' directly, which slightly weakens the mapping.

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?

States a specific verb and resource: extract all regular files from the active archive or application package into a fresh temporary directory, with the location returned. The scope (regular files, active archive/application package) implicitly separates it from extract_firmware, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

The phrase 'active archive or application package' gives context for when the tool applies, but there is no explicit when-to-use, when-not, or named alternative such as extract_firmware or inspect_artifact. The agent must infer that this is the materialization step preceding inspection.

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