read_v2_python_program_build

Returns the caller-owned build state and sealed plan digest when available. A build still pending or failed cannot be treated as a sealed executable plan.

These signatures come from local MCP tool discovery. Use the signature registered by your deployment and confirm your identity and permissions before calling the tool.

Endpoint signatures and example arguments

Examples show the arguments to the tool. Replace placeholder IDs and illustrative revisions with values from your authorized disposable scope.

{
  "build_id": "{{build_id}}"
}

{
  "properties": {
    "build_id": {
      "title": "Build Id",
      "type": "string"
    }
  },
  "required": [
    "build_id"
  ],
  "title": "read_v2_python_program_buildArguments",
  "type": "object"
}

{
  "workspace_id": "{{workspace_id}}",
  "application_id": "operating-cube",
  "build_id": "{{build_id}}"
}

{
  "properties": {
    "workspace_id": {
      "title": "Workspace Id",
      "type": "string"
    },
    "application_id": {
      "title": "Application Id",
      "type": "string"
    },
    "build_id": {
      "title": "Build Id",
      "type": "string"
    }
  },
  "required": [
    "workspace_id",
    "application_id",
    "build_id"
  ],
  "title": "read_v2_python_program_buildArguments",
  "type": "object"
}

Handling errors

MCP_TOOL_CAPACITY_NOT_DISPATCHED means the server did not dispatch this call. MCP_TOOL_DEADLINE_OUTCOME_UNKNOWN or MCP_TOOL_PROCESS_FAILED_OUTCOME_UNKNOWN leaves the outcome unknown. For a call with effects, reconcile the original request before starting a new one. For a scoped denial, verify the caller's grant and the selected target.

Module guidelines · Related workflow · Application-language function catalog