Skip to main content
Glama

artifact_register

DestructiveIdempotent

Links a simulation output to requirement IDs, source files, and verification evidence, so results are traceable and requirements can be reviewed against actual hashes.

Instructions

Link an actual output to the user's requirement IDs, source files and verification evidence.

path, sources and checks[].evidence are project-relative. The service reads their hashes; do not calculate or repeat hashes in the request. Each check is {'receipt_id': 'check_...'} from check_run/check_get. The receipt must include this artifact and its actual sources. Service-derived measurements determine passed. Historical passed/method/evidence claims are retained as unverified and cannot complete a requirement. The latest registration for this path supplies its current checks and complete requirement_ids. Earlier verdicts remain in history. A failed current check blocks its linked requirements and reopens a completed task; record corrected evidence before re-reviewing. An analysis result path normally starts with analysis/<operation_id>/. Returns the new task revision. description labels the result for users. supersedes explicitly replaces earlier artifact IDs with a revised output, preserving their files/reviews. Replacement must retain their requirement IDs. Other results remain current.

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": {
      "task_id": "<task_id>",
      "revision": "<revision>",
      "path": "<path>",
      "sources": "<sources>",
      "requirement_ids": "<requirement_ids>",
      "checks": "<checks>",
      "op_id": "<op_id>"
    },
    "name": "artifact_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
op_idYes
tokenNo
checksYes
sourcesYes
task_idYes
revisionYes
supersedesNo
descriptionNo
requirement_idsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the destructive/idempotent annotations, it discloses that the service reads hashes rather than trusting submitted ones, that passed is service-derived, that historical claims are retained as unverified and cannot complete a requirement, that the latest registration supplies current checks, and that a failed check blocks requirements and reopens a completed task. These are non-obvious consequences an agent cannot infer from the annotations alone.

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?

Length is justified for a 10-parameter destructive mutation tool, and the core purpose is front-loaded. A few sentences are clipped to the point of ambiguity, such as 'Other results remain current.' and 'Service-derived measurements determine passed.'

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?

An output schema exists, so return-value detail is not required, though it still notes the new task revision is returned. The main remaining gap is the undocumented op_id/token/revision semantics, which matter for a task-revision-sensitive mutation.

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 carry parameter meaning. It explains path, sources, checks[].evidence, requirement_ids, description and supersedes well, but leaves op_id, token, revision and task_id entirely unexplained despite being required inputs.

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 opening sentence gives a specific verb and resource: link an actual output to requirement IDs, source files and verification evidence. It does not explicitly contrast itself with nearby tools such as artifact_preview, though it does position checks as coming from check_run/check_get, which clarifies its role in the pipeline.

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?

It states concrete conditions: checks must be receipt_ids from check_run/check_get, the receipt must include this artifact and its sources, corrected evidence must be recorded after a failed check, and supersedes must be used for revised outputs retaining requirement IDs. Missing is an explicit statement of when NOT to register here versus other registration tools.

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