Skip to main content
Glama

get_render_artifact

Download a manifest-listed render artifact in 256 KiB chunks with whole and per-chunk SHA-256 verification for reliable retrieval.

Instructions

Download a manifest-listed render artifact in at most 256 KiB chunks, with whole/chunk SHA-256.

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

Input Schema

NameRequiredDescriptionDefault
job_idYes
lengthNo
offsetNo
artifact_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the 256 KiB chunk ceiling and SHA-256 verification at both whole-artifact and chunk level, which implies a safe read operation. It omits how the caller detects completion, behavior on out-of-range offsets, and any auth or rate-limit constraints.

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?

A single dense sentence with the core action and its key constraints front-loaded; nothing is padded. The trailing 'with whole/chunk SHA-256' is telegraphic and slightly obscures meaning, keeping it from a 5.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and the chunking model is captured. However, for a paged binary-download tool with zero schema coverage, the definition leaves the caller without completion criteria or the role of each identifier.

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 for all four parameters. It effectively explains 'length' and 'offset' (256 KiB chunk cap corresponds to the default 262144, and chunks imply offset/length paging), but adds nothing about the distinction between job_id and artifact_id.

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 gives a concrete verb and resource ('Download a manifest-listed render artifact') plus a scoping trait (chunked, checksummed). It is distinguishable from a plain 'get_artifact' only by inference from the manifest/chunk wording, so sibling differentiation is implicit 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?

Usage is implied rather than prescribed: 'manifest-listed' suggests the artifact must come from a manifest, and chunking implies large files. There is no explicit statement of when to use this instead of the sibling get_artifact, nor any exclusion or prerequisite guidance.

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