Skip to main content
Glama

get_artifact

Read-onlyIdempotent

Retrieve artifact metadata and the download API URL, then fetch the file bytes with a two-step presigned GET flow. Use it to locate and download task artifacts safely.

Instructions

Get artifact details. The bytes are never inlined: download them with the two GETs below. Downloading an artifact is two GETs. Step 1: GET /api/v1/artifacts//download with header X-Agent-Key: -> 200 JSON {"url": ""}. Step 2: GET that url with NO headers -> 200, the file bytes. Pitfalls: on step 1 only X-Agent-Key is accepted (X-API-Key and Authorization: Bearer give 401); on step 2 any extra header, Authorization in particular, breaks the presigned signature (400). The artifact's download_path is step 1's path. browser_only_url is a human page and answers 401 to an agent key by design.

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

Input Schema

NameRequiredDescriptionDefault
artifact_idYesArtifact ID.
include_contentNoAdds download_api_url: step 1 of the download (the API endpoint you call with X-Agent-Key), NOT the file and NOT a link to open. The bytes are never inlined.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare this a safe read-only, idempotent operation, and the description goes far beyond them: it discloses the exact auth header accepted on step 1 (X-Agent-Key only) and the specific failure modes for wrong credentials (401) and extra headers on step 2 (400 signature break). These are non-obvious operational traps an agent would otherwise hit.

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 critical constraint (bytes never inlined) is front-loaded, and the numbered two-step flow is easy to follow. There is some redundancy — 'Downloading an artifact is two GETs' restates 'the bytes are never inlined: download them with the two GETs below' — but the procedural detail earns most of its length.

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?

With no output schema, the description does not enumerate the metadata fields returned by the tool itself (only mentioning download_path and browser_only_url), so an agent can't fully anticipate the response shape. For a read-only lookup with full param coverage, though, everything needed to call it correctly is present.

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 100%, so both parameters are already documented. The description nonetheless adds real meaning to include_content by stating download_api_url is the step-1 API endpoint, 'NOT the file and NOT a link to open', correcting a likely misinterpretation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get artifact details'), and immediately clarifies scope by saying 'the bytes are never inlined' — distinguishing it from a content-fetch tool and implicitly from the sibling list_artifacts. An agent can tell what it returns (metadata) versus what it does not (file bytes) without opening the 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?

Clearly signals when this tool is not enough: to actually obtain bytes the agent must follow the two-GET flow, and browser_only_url is explicitly called out as a human page that will not work for an agent. It lacks an explicit routing sentence to list_artifacts for enumeration, which keeps it from a 5.

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