Skip to main content
Glama

artifact_read

Read-onlyIdempotent

Load a previously generated context artifact by ID to reuse task packets, repo maps, and decisions without regenerating them.

Instructions

Load a previously generated context artifact by ID so agents can reuse earlier task packets, repo maps, and decisions without regenerating them.

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": {
      "artifact_id": "<artifact_id>"
    },
    "name": "artifact_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
rootNoAbsolute project root. Omit only where this session started; required elsewhere and on every subagent call.
artifact_idYesArtifact ID returned by repo_map, search, task_pack, change_impact, edit_scope, or decision_brief.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.0
    • changedInput schema / properties / root / description
      Previous value: -"Absolute project root. Required with linked worktrees; subagents must pass their own worktree root on every call."New value: +"Absolute project root. Omit only where this session started; required elsewhere and on every subagent call."
  2. First observedv1.4.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world scope, so the safety profile is fully covered structurally. The description adds the useful framing that artifacts are reusable outputs of prior tools, but says nothing about behavior such as an unknown/expired artifact ID or whether reads are cached.

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?

A single well-formed sentence with the load action front-loaded and the motivation trailing. No filler, no redundancy with structured fields.

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 simple two-parameter read tool with full schema coverage, complete annotations, and no output schema requirement, this description covers what the tool is and why an agent would call it. Only edge-case behavior (missing artifact) is unaddressed, which is minor.

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 100%, so both parameters are already documented, including which tools return valid artifact IDs and the root scoping rule for subagents. The description's 'by ID' adds nothing beyond the schema, so the baseline of 3 applies.

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 ('Load') and resource ('previously generated context artifact by ID') and enumerates what an artifact can be (task packets, repo maps, decisions). It's clearly a retrieval tool, though it never names or distinguishes itself from siblings like memory_record_task or task_pack.

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 clause 'so agents can reuse earlier task packets... without regenerating them' implies the when-to-use case (reuse vs. regenerate), but there is no explicit when-not, no prerequisite call ordering, and no named alternative. Usage is inferable rather than specified.

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