Skip to main content
Glama

get_artifacts

Retrieve a run's task contract, candidate version, changed files, and independent check evidence to review handoff results and verify completed work.

Instructions

Get task contract, candidate version, changed files and independent check evidence.

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": {
      "run_id": "<run_id>"
    },
    "name": "get_artifacts"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It discloses what is returned, which helps, but says nothing about permissions, whether results are scoped to the given run, pagination, size, or behavior when artifacts are missing.

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 front-loaded sentence with no filler; the listed artifacts are the most useful information and come first. It is terse almost to a fault but wastes no words.

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?

With no output schema and no annotations, the description is the only documentation, and it covers the returned contents but not format, error behavior, or how it differs from get_diff/get_context. Adequate for a one-parameter read, but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the only parameter, run_id, receives no elucidation in the description. The name is largely self-explanatory, but nothing is added about expected format or whether it is a run identifier from list_runs.

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 names a concrete verb ('Get') and enumerates the specific artifacts returned: task contract, candidate version, changed files, and independent check evidence. That is far more informative than the bare name, though it doesn't distinguish the overlapping 'changed files' from sibling get_diff.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool over get_diff, get_context, or get_run, even though their scopes plausibly overlap. The agent must infer selection from the enumerated contents alone.

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