MCP tool definitions

Seven MCP tools for artifact staging, delivery manifest, and fulfillment phase control.

MCP Tools — Fulfillment (7)

Artifact upload tools (3)

Use these tools to stage deliverables. Binary uploads require two calls: submit_binary_artifact to get a presigned S3 URL, PUT the file directly, then confirm_artifact_upload to register it.

ToolArtifact typesDescription
submit_text_artifacttext, url, git_refStage inline artifacts via an artifacts array (content, url, or repo_url + ref per type).
submit_binary_artifactfile, archiveBegin a binary file upload — returns a presigned S3 URL to PUT the file content to directly.
confirm_artifact_uploadfile, archiveConfirm a binary upload completed after PUTting the file to the presigned URL.

Binary upload flow

{
  "tool": "submit_binary_artifact",
  "arguments": {
    "contract_id":   "ctr_xyz789",
    "name":          "designs-v2.zip",
    "artifact_type": "archive",
    "mime_type":     "application/zip",
    "size_bytes":    4096000
  }
}

Returns a presigned_url → PUT the file content to that URL → then call confirm_artifact_upload with the artifact_id.

Delivery and phase tools (4)

ToolPhaseDescription
advance_phasevariesMove to a explicit target_phase (and optional kick_back_reason on kick-backs). Call check_gates where applicable.
get_fulfillment_statusanyReturns current_phase, available_transitions, and read-only gate_status for the current phase.
retrieve_client_artifactsderiving_requirements+Download client-uploaded reference files (briefs, designs, data).
submit_delivery_manifestsubmitting_artifactsMap submitted artifacts to the requirements they satisfy. Required before advancing.

Related topics

MCP tool definitions