Skip to main content
Glama

Download Grok Bot artifacts

download_grok_artifacts

Downloads a request's artifact files to a local folder, verifies each sha256, and returns local paths for reading; optionally fetch only specified artifact names.

Instructions

Download a request's artifact files to a local folder (default ~/grok-relay-artifacts/<request_id>/), verifying each sha256. Returns the local paths so you can Read them. Optionally pass names to fetch only some files.

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": {
      "request_id": "<request_id>"
    },
    "name": "download_grok_artifacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesNoOnly download these artifact names. Default: all.
dest_dirNoLocal folder to save into. Default ~/grok-relay-artifacts/<request_id>/.
request_idYesThe request_id of the task.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/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 behavioral burden. It usefully discloses the default local write path, sha256 verification, and the return value shape, but says nothing about overwrite behavior for existing files, permissions/auth requirements, size or rate limits, or what happens on a checksum mismatch.

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?

Three short sentences, front-loaded with the action and destination, then the verification/return contract, then the optional narrowing flag. No filler or repetition.

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 3-parameter download tool with no output schema, the description covers where files go, integrity verification, and the return value, which is what an agent needs to call it and use the result. Only failure and overwrite semantics are absent, a minor gap given the tool's simplicity.

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 coverage is 100%, and the description largely restates what the schema already documents for names and dest_dir (partial fetch, default path). It adds no formatting, path-resolution, or edge-case semantics beyond the structured fields, so the baseline 3 applies.

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 ("Download a request's artifact files"), names the destination and scoping, and makes the effect concrete (files land locally, sha256 verified, returns paths). It is clearly separable from list_grok_artifacts and get_grok_result without opening either 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?

Implies the use case by saying it returns local paths "so you can Read them" and explains the partial-fetch option via names. It does not explicitly say when not to use it or point at list_grok_artifacts as the way to discover names before downloading, so guidance is clear but not exhaustive.

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